3 ms·
The thesis that LLMs generating code will eat no-code could be right. But I'm not sure about this GenSX thing. I looked at the docs briefly, but wasn't able to
by akoboldfrying 2y ago
The thesis that LLMs generating code will eat no-code could be right.
But I'm not sure about this GenSX thing. I looked at the docs briefly, but wasn't able to figure out what using JSX syntax adds over just using plain old function calls. Convenient named parameters? But you can already effectively get that in TS just by passing an object and treating its fields as parameters. There does seem to be some automatic stream handling, which might be handy.
(I suppose you could make the same criticism of React, but I think the answer is clearer there: You're gonna wind up with HTML, and JSX gives you convenient HTML syntax for making the parts.)
- evboyle 2y agoAuthor of GenSX here. It turns out that react's programming model is great at constructing and executing DAGs. The resulting code is much simpler, and more expressive. And the React's focus of composition over abstraction is 100% what you need in the LLM world. It enables sharing code across large teams by default. When you have serializable props, outputs, and pure functions (properties of both the React and GenSX component model) then it is trivial to layer things like durable execution on top of it. Might give you an idea of what is soon to come!