31–40 of 54 posts
The Deno runtime is great for workflows because Deno is lightweight and can import modules using arbitrary URLs.
I'm doing something[0] similar with Deno, currently it configures workflows based on yaml files, but my goal is to make a gui tool to help generate yaml config files. My work is still very early stage, currently it can use any remote Deno module or typescript/javascript to execute steps and fetch and filter source data. The Deno runtime is great for workflows because Deno is lightweight and can import modules using a…
Scripts from another dimension, now in Python. https://scriptsofanotherdimension.tumblr.com/
These kinds of visual programming systems always seem to degrade into spaghetti hell, don't they?
And my home alarm system flow: https://pictshare.net/82qfpa.png
To be fair though you can create sub-flows to have it more compact but when I designed it, I didn't know about theseyet
Earlier quoted context omitted.
Like comparing Word to Latex. Latex is faster when you know it.
Scientific literature seems to disagree with this statement: "An Efficiency Comparison of Document Preparation Systems Used in Academic Research and Development" [1] For example, amount of written text was higher among Word novices than among LaTeX experts, with overall less mistakes. The only category where LaTeX users produced more content than Word users was equation text, and even in that case, authors suggest th…
It looks nice. If UI performance is a concern, one could move the GUI part to C++ and do some quick pybind11 Python bindings for better performance. I've used this C++ ImGui node editor with similar features for some hacky synthesizer gui using this library: https://github.com/thedmd/imgui-node-editor
Very cool. We're designing an open source automations engine for Kubernetes ("Zapier/IFTTT for devops") and have thought about adding a UI for automating stuff visually. So far, simple YAML configurations have won out and we're still debating the benefits of a UI. Does anyone have experience using tools like this at scale or for technical domains? (E.g. devops.) Would love to hear a convincing case why a UI is better…
I think the key here, as a responsible developer, is ensuring isomorphism between the GUI representation and the generated code. To the extent that the development method could be swapped without repercussion. Most GUI tools, presumably in speed to market, skip this. But as soon as you've created something that can only be viewed & modified in a visual editor... you've become part of the problem. So I'd approach this…
Why is that? You don't view the bytes your text editor generates do you?
Earlier quoted context omitted.
I think the key here, as a responsible developer, is ensuring isomorphism between the GUI representation and the generated code. To the extent that the development method could be swapped without repercussion. Most GUI tools, presumably in speed to market, skip this. But as soon as you've created something that can only be viewed & modified in a visual editor... you've become part of the problem. So I'd approach this…
> But as soon as you've created something that can only be viewed & modified in a visual editor... you've become part of the problem. Why is that? You don't view the bytes your text editor generates do you?
Earlier quoted context omitted.
I work in the software side of the same field and visual flow programming tools like this help bioinformatics and scientists visualise analytics code bases, but they're not sold well to customers. Somehow the teams that sell these products still think in terms of low code or data science, when they probably should be speaking in terms of translational medicine
Talend is sold sort of well (ex. https://help.talend.com/r/mjoDghHoMPI0yuyZ83a13Q/YYVSsDiyJ3v... )
Have a look at FME by SAFE software if you want to see what a better, more well looked after version of what Talend could look like is.
Earlier quoted context omitted.
Like comparing Word to Latex. Latex is faster when you know it.
Scientific literature seems to disagree with this statement: "An Efficiency Comparison of Document Preparation Systems Used in Academic Research and Development" [1] For example, amount of written text was higher among Word novices than among LaTeX experts, with overall less mistakes. The only category where LaTeX users produced more content than Word users was equation text, and even in that case, authors suggest th…
I wonder how they incorporated that into their productivity metrics
As an aside, I have used a workflow where I give someone a a paper to review as an overleaf project, they make all their changes, and then I merge it back into my work picking and choosing the bits I want. And this all works fairly nicely since overleaf has support for git.
