To elaborate further: I don't believe ecosystem is king. Success can mean different things to different people, and is not always a single dimension of "popularity units".
> I’ve had to deal with a nightmare Elm project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.
I’ve had to deal with a nightmare React project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.
Source: 7 years of Haskell in production
shipping as wasm is not an option as it increase bundle size for very little gain (unless you're running something super performance intensive).
We would need a bridge between sane languages and a JS framework, not just JS in general.
5 years ago I would have done a Haskell -> hyperscript bridge to build frontend applications. Today I would do a Rust -> Solid.js bridge to build frontend applications.
Logic could be compiled down to JS, UI could be compiled to Solid.js components.
Less popular platforms will get more isolated rather than less as the wave of generated code that “works out the box” only works with stuff like react…
Not a single bit of "React" in the code. It has absolutely NOTHING to do with React. But I've seen it in projects I've inherited... just because, "we're using React, may as well get the React version of the library".