That said, you can get plenty of mileage out of using React as a frontend and wasm for the application core. I believe this is what Figma does. And you can sidestep the DOM entirely and use your own UI renderer, which seems to be what Adobe is doing here. https://makepad.dev/ is another (absurdly impressive) example of that approach, but that's a very involved approach!
WASM still has no concept of garbage collection which means that by default it’s limited to a smallish number of languages that are viable. That’s changing in the not too distant future it seems as the plans for garbage collection are well underway already.
It also has no ability to do DOM manipulation meaning you end up in a scenario like the one in the article where “algorithms” end up in wasm and the UI in web components / JS.
I believe that too is going to change at some point.
As for where things stand RIGHT now in 2021 if you want to skip JS I would say it probably depends a lot on what you want to build. I think for a lot of B2B enterprisey apps that mostly run on Desktop devices Flutter is already a viable option there and generally a much nicer experience.
The performance / accessibility right now isn’t at a level where it would make sense for a bunch of other options but as I mentioned elsewhere in this thread it is barely out of beta by a couple of months. It’s improving a lot at a pretty rapid pace and is built upon solid tech choices and open standards. I think it has a decent future ahead of it.
Flutter is great except for Dart - another language.
I’m happy to say when I’m wrong though, it ended up as probably my favourite language of all after not too long.
It’s often described as the love child of Java and JavaScript where they took the best from both and got rid of the most hated parts of both too. But it ends up as a really nice and performant language to build apps in and is supported by a lot of amazing dev tooling to make life easier.
[1] https://www.figma.com/blog/building-a-professional-design-to...