I just want to be able to embed diagrams in my code files.
We need visual programming. No, not like that
461–470 of 505 posts
Re: We need visual programming. No, not like that
#462There are three benefits - Understanding the codebase (even to plug in a new feature), Findings issues easier and I can't emphasize this enough - We can/need reach into newer complexities that we thought twice about maintainability. In summary, We can reduce threshold for developer expertise to onboard into complex codebases - freeing up, developers on the other side to tackle far greater problems.
Re: We need visual programming. No, not like that
#463Earlier quoted context omitted.
> Schematix provides diagrams as a dynamic resource using its API. They aren't images you export, they don't end up in My Documents. This isn't Corel Draw. In Schematix, you specify part of your model using a graph expression, and the system automatically generates a diagram of the objects and relations that match. As your Schematix model changes, the results of the graph expression may change, and thus the visual di…
Schematix is somewhat unique. Direct competitors? -- not exactly, but IT asset managers, DCIM, BC/DR tools, and CMDBs are all competitors to some degree. Some of our best users are professional consultants who use us for a project which often introduces us to a new customer. A Show HN would certainly be in order. Thanks for the thoughts!
Re: We need visual programming. No, not like that
#464I really miss ObjecTime ROOM. We used it a lot for embedded software development and it basically allowed to model the "big picture" of your application in (extended) UML and add C / C++ for the details. The generated code for the rest was usually very efficient, the runtime was pretty portable and slim as well. It became IBM Rational Rose Realtime (! the last word makes a big difference) and then it kind of disappea…
Have you used the QP framework ( https://www.state-machine.com/ )? It supports UML hierarchal state machines with code generation. One embedded dev I know shipped a couple products with it and still likes it.
Re: We need visual programming. No, not like that
#465As someone with a hardware background, I'll throw in my $0.02. The schematic capture elements to connect up large blocks of HDL with a ton of I/O going everywhere are one of the few applications of visual programming that I like. Once you get past defining the block behaviors in HDL, instantiation can become tedious and error-prone in text, since the tools all kinda suck with very little hinting or argument checking,…
As much as I prefer to do everything in a text editor and use open-source EDA tools/linters/language servers, Xilinx's Vivado deserves major credit from me for its block editor, schematic view, and implementation view. For complex tasks like connecting AXI, SoC, memory, and custom IP components together, things like bussed wires and ports, as well as GUI configurators, make the process of getting something up and run…
"Free idea: do all this work that it takes hundreds of people to do. Free! It's even free! And easy!"
Lol you must be one of those "the idea is worth more than the implementation types.
Re: We need visual programming. No, not like that
#466Re: We need visual programming. No, not like that
#467Re: We need visual programming. No, not like that
#468Earlier quoted context omitted.
Ok, when can we meet? I have never seen it work, and, as said, I review 100s of project a year; everything ts is super slow so far. Maybe you have something.
Their hot reload cycle is fast because esbuild doesn't type check the code, it just removes types from Typescript so it turns into JS (it may do minification and tree shaking but in dev, they probably remove that). I've written some esbuild plugins and can confirm that on incremental builds, esbuild will probably never take more than a few ms even on larger projects (because it doesn't matter how big your project is,…
Download some horror show like Unkey and show a video of its millisecond hot reload…
Re: We need visual programming. No, not like that
#469Earlier quoted context omitted.
Yes, you do if you want to make money on decades timescales instead of some grifter vc 2 year thingy.
Unfortunately you end up selling your stuff to people building missiles and bombs that way—witness CompCert and Frama-C.
Re: We need visual programming. No, not like that
#470Far more important is instant feedback and that’s getting worse all the time: with lisp, smalltalk, Delphi, forth things were instant. With typescript or rust etc, if the project is larger than hello world, the feedback is well, far from instant. Bret victor talked about feedback, not necessarily visual programming and for some reason we are making things worse instead of better. When I show a Common Lisp dev session…