@erdemwrites · X

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

dylansuttonc · HN

When I started programming Edge Python more than six months ago, I was looking for a version of Python that weighed less than 200 kb so it could reach any device, sandboxed by design, built with browsers in mind, decoupled from the operating system and very fast. Today the closest competitor would be MicroPython. However, it did not solve my real problems or the problems of the people who use the project. * Managing async and blocking code on the event loop. MicroPython inherits CPython's blocki

@fortsignal1 · X

@spec_tacul_ar · X

Specifications for humans and AI.