I was stuck once by abusing `bind:` and other time with global exit transitions + sveltekit routing, but that's about it.
React on the other hand feels like a pot warming up and we're the frogs being boiled alive at this point. You can write some perfectly valid, but naive React code and it's going to have some footguns. We're so used to write idiomatic React code we don't even notice that anymore. You learn to use stable references in callback functions, to be careful using Context, and so on. But the list is not short, and it only grows.
Wanna write some naive code in svelte two days in? There's a good chance it's the same code you'd write a year later. Maybe that's what people mean by "just JS".
AFAIK WebAssembly can't do more harm than JS since it lives in the same sandbox, so that's not a concern? You're basically running Flash in a small VM.
1. ...but why give them ability to charge based on what you're doing with access they give you? It's like your electric power provider would charge you more if you have a blacklisted freezer...
2. ...but maybe let's start by lowering the bar for new ISPs and getting rid of monopolies instead of giving them more means to squeeze more money? How getting rid of NN helps with that? Google couldn't get into that market.
3. ...but what if my provider throttles wired network, not wireless, and not 4k, but full HD? What if they throttle my twitch, because they got a deal with google to serve unlimited access to Youtube Gaming at the cost of limiting access to twitch? Sure, change IPS! Whoops, there's no competition in my area. What now?
Two-way data binding is only syntactic sugar for setting value as a property and assigning it's value on event listener. You can read about it in the docs
Sunway TaihuLight (the most powerful supercomputer right now) was benchmarked to have 93 petaflops[1].
The cost was 1.8 billion Yuan (US$273 million). So cheap I guess.