Immediately after switching the page, it will work with CSR.
Please reload your browser to see how it works.

Source:https://github.com/SoraKumo001/next-streaming

⬅️ Show HN: Turn any workflow diagram into compilable, running and stateful code
raydenvm 2 hoursReload
This reminds me of the UML/RUP era from the early 2000s.... Is that an attempt to revive or even resurrect UML diagrams and Rational Unified Process blending it with AI? I would bet it's all dead forever. I'm skeptical about diagram-driven development making a comeback. In my experience, developers today prefer more agile, code-first approaches because requirements change rapidly and maintaining diagram-code synchronization is an unbearable challenge.

mpetrovich 3 hoursReload
Some feedback: show example input & output without requiring me to create an account.

Looks interesting, best of luck!


sky2224 2 hoursReload
This is cool. I remember not too long ago I had a professor telling me that this was essentially the future of software engineering and that soon we won't be writing code as we know it today. I believed him, I just didn't think we'd be seeing it here so soon.

Any plans to create systems that allow this to be embedded in existing code bases? It'd be neat to be able to sketch out new systems that your tool could generate code for that seamlessly hooks into an existing system's architecture, especially if it could have a UX similar to how copilot or cursor behave in how they're directly inline with the code.


potamic 6 hoursReload
This is really cool as far as the application goes, but I do have a question on how you plan to compete/differentiate, if at all. I fed the same image to one of the flagship LLMs and was able to generate, more or less, the same dapr scaffold. You might probably be able to fine tune towards dapr use case better, but if one of the flagship models that people already use is going to come close, then it becomes a hard sell.

I suppose it's also a general question about the many new AI applications in the market, because these flagship models are getting really good by the day, and seem to be eating up into each and every of those use cases.


swyx 6 hoursReload
1. yeah this is nice, making it easier to generate workflows is always good. i think the challenge is always versioning and proper error handling - if the diagram the user sends in doesnt properly model the work done, then you're SOL.

2. (sorry to bring it up but have to ask) how does Diagrid/Dapr compare to Temporal? i browsed your docs but there wasn't much that came up. is Dapr strictly dag based?