Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you enjoy this approach, you might enjoy the Crank JS framework. https://crank.js.org/

> Crank uses generator functions to define stateful components. You store state in local variables, and `yield` rather than `return` to keep it around.



I started experimenting with this recently. Neither my knowledge nor the maturity is at a level where I would use it for production work but there are definitely some promising aspects to this. I am preparing a talk about it.

The most significant unknown for me is how state management (like Redux etc.) would work in a larger app. I can think of many solutions but I can't figure out whether the tradeoffs then result in a net gain or loss.


The coolest thing (IMO) compared to react is the ability to await inside a component.


I believe react has that now with the use hook.


I love this for some reason. However, I wonder if it would end up being more complicated than React in practice. I generally prefer pedantic/stricter usage guidelines/conventions.


I think this is my first time seeing techniques like “for ({} of this) {…}”, very interesting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: