I think the real failure is not wholly technical. e.g. job,mainstream pressure
<imagine ceo ask why not react?>
What's important but underlooked.
1. founder of language don't hv time to add power tools into existing core language. one way or the other, you say we hv X that does same job. but actually not the same.
---result
LOC point of view, react has 100 less code for button. Elm has good functional style, however distance(html, elm template) > distance(html,react). So, elm has "too much" high level built-in abstraction, which makes code reading harder.
---my take
react is ok in most of cases
react native is great (but you will end up writing large screen adaption, native feature for hardware X, shipping web code to native app user is ok, reverse not true).
react hook is horrible (checkout some ecommerce oss, 100 warning after compile, 10+ hooks in same component, communication that not to trigger rerendering)
vue has more consistency but 0 in native app direction unless you happy with doing everything in web
angular was great until ppl left it to maintanance mode. tooling is very complete. (stencil,ionic)
kotlin could be better glue between js and native. it makes code cleaner, easier.
community,design,rules,tools are mutiple goals when dev picking up new tooling. https://www.youtube.com/watch?v=oYk8CKH7OhE
I think the real failure is not wholly technical. e.g. job,mainstream pressure <imagine ceo ask why not react?>
What's important but underlooked. 1. founder of language don't hv time to add power tools into existing core language. one way or the other, you say we hv X that does same job. but actually not the same.
2. hype disappear after a while (fp hype)
3. code comparison
e.g. rewrite in diff ways of prod code
elm ver: https://github.com/cultureamp/kaizen-design-system/blob/3ac2...
react ver: https://github.com/cultureamp/kaizen-design-system/blob/3ac2...
---result LOC point of view, react has 100 less code for button. Elm has good functional style, however distance(html, elm template) > distance(html,react). So, elm has "too much" high level built-in abstraction, which makes code reading harder.
---my take react is ok in most of cases
react native is great (but you will end up writing large screen adaption, native feature for hardware X, shipping web code to native app user is ok, reverse not true).
react hook is horrible (checkout some ecommerce oss, 100 warning after compile, 10+ hooks in same component, communication that not to trigger rerendering)
vue has more consistency but 0 in native app direction unless you happy with doing everything in web
angular was great until ppl left it to maintanance mode. tooling is very complete. (stencil,ionic)
kotlin could be better glue between js and native. it makes code cleaner, easier.
typescript is a noise :[ yey