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

Nah, I still think React made the right choice. I used to use functional languages so coming to the JS world and seeing that no lessons from that world were learned was disheartening. React, where UI = f(state), is an amazing model compared to the imperative jQuery model of before.


You may prefer it to jQuery's model, but that doesn't make React's model good.

Try SolidJS. Similar ethos to React but far less boilerplate and performance-killing repaints.

Less code is better, functional or not.


Sure it does, it is good because it's functional. I could similarly write a convoluted yet highly short Perl expression, less code is not always better.

I tried Solid. Signals are not new, I've used Knockout before and it turns into a spaghetti mess after a few years. I guess people today simply aren't old enough or experienced enough to know what eventually happens with fine grained reactivity.



That page doesn't really answer why it can solve the issues of Knockout better. Eventually the same problems will arise, of spaghetti code among things reacting to other things reacting to yet more things.




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

Search: