Nowhere I have stated this is the clear path to AGI and you are right, we are missing key building blocks. But I feel like there's too much skepticism agains this field while the advancements are not appreciated enough.

I don't know either what will lead there, but I see more and more examples of different networks being combined to achieve more than they are capable of individually.

SPA-s are much-much harder to develop if more teams are working on it. So your first sentence makes little sense.

> companies move everything to client-side in order to reduce Amazon bills

This is never the reason why it happens. Seriously? The cost are not saved, just moved around. SPA-s are developed because they could provide a much better UX. As a side benefit, server side development becomes simpler by providing some REST or GraphQL API. You don't want to be in a place where tens of thousands of lines are generated backend side by backend developers.

> client-side scripts are poorly optimized and contribute to global warming by causing hundred thousands machines to spin up their CPU fans.

I appreciate your sense of humor :D

Edit: with chrome extensions, I can inject a script tag from any domain to any page. I used that to inject a lib from CDN JS, but recognized it's silly and imported the package instead.

I've seen that blog post where a guy demonstrated that many UI elements can be done with CSS, I like that. I try to do that myself as much as I can, but let's not pretend that CSS is a programming language and it can replace ANY JavaScript.

For example create a melody with seed: 4564342

The client can render it and if you access it from the server the server does the rendering with the same seed.

Caches also exists, now with PWA-s offline modes would benefit from the History API.

Not sure about your point, the history API improves UX if you do it right:

https://developer.mozilla.org/en-US/docs/Web/API/History_API

It does everything as hand written, pure HTML page would, just do it faster.

But there probably always will be a safe flag that generates everywhere running binaries.

Regardless of is this a trap or not, it's obvious to me that developers want simplicity and consistency. WA provides both so don't wonder why it's taking off.

> So instead of Linux/Windows/OSX we will have Firefox/Safari/Chrome/Whatever all with their own implementation gotchas

I let the compilers worry about this :)

https://github.com/anderejd/electron-wasm-rust-example

https://github.com/martinjackson/electron-run-shell-example

> And worst of all, your feathers will get plucked by people who do, and you may never even realize it.

As someone who has little clue about accounting, what does this even mean? You mean I can be easily ticked by a shady partner?

By the way you are right, my side projects are stuck at the part when I have to ask for money :)

Probably the huge amount of bureaucracy and regulation keeps medical focused IT in its shit pool of separate islands.

Maybe you should campaign for state regulation mandating to create a HMTL / W3 like standard for data sharing that's mandatory to use.

> ...until you submit it to an executor

That's not much different. Don't call the function then which returns that promise :)

Or you can write:

    sendRequest(thingThatReturnsPromise);