I really haven't done much comparison between the low level mechanisms in, say, react. My understanding is that it's a bit simpler, but does it handle all of the whacky corner cases with changing select options around and changes around inputs, for instance?
I'm starting to see some distinction between libraries being designed for websites vs for webapps. For instance, I don't think you can get much better than svelte for lightweight general web-facing stuff. For much more complex apps though, you start to hit a wall with what's possible without gaining weight pretty fast.
The first libraries that came out didn't make a direct distinction, though I feel like angular definitely is aimed at apps.
All the super lightweight libs that are popping up now seem to be targeting less app-y environments.
Both, but most of my business is in the app area. Strangely, my biggest existing codebase is a cms that uses ractive on both sides - designers define 'components' (template + script + style + user config, not ractive components), which they or end users can assemble into pages. That could really be done with any lib, but ractive is extremely designer friendly.
We're also migrating a bunch legacy desktop apps into the interwebs era, and that's where the webapp-friendly facets of ractive are super handy. For instance, a deep data model with binding all the way down fits graphs of business objects beautifully.
Mostly in the app arena. Usually use Ractive to do quick proof of concepts about components (reuse, portability, data management, styling, how to do a workflow) because it can do almost anything and without a build step (or at least only needs bundling). Projects are usually Angular tho because it's the Java for webapps. :D
I'm still not sure what's going to take over computationally intensive backends for us: .net core, rust, or maybe kotlin. If MS commits hard to .net core it could be pretty good. Hopefully they won't take their usual approach of decent ideas followed by a Molotov cocktail in a dumpster. What sorts of backends do you use?
Node definitely has a short spin up advantage. You have to watch your modules, though. There's a pretty extensive ecosystem, but I prefer modules with very minimal deps and still get bitten occasionally. PHP has improved vastly in the years since I last used it 😁.