If Microsoft was not aligned with developers in the early 2000's, that failure is on them.
If Microsoft was not aligned with developers in the early 2000's, that failure is on them.
Plenty of historical attempts to dive into, since 1958.
Now we have startups redoing Java and .NET application servers, with Kubernetes, WebAssembly, WASI, and YAML spaghetti, because that is so much better.
Edge devices running bytecode? That is so last century.
Edge devices running bytecode has its uses. Being an old idea doesn’t discredit it (neural networks were first described in the 70s)
At least WASI is a standard unlike flash or Java applets.
Maybe “open spec” or “open standard” is better.
The most exciting part about WASI for me, though, is that it's sticking to a capability-based interface and it's actually gaining a lot of traction. There are few examples of capability systems getting as much attention as this.
Is the idea mainly that permissions are more fine-grained? It probably makes porting existing applications tricky, though, right?
It is like microservices bandwagon nowadays, apparently distributed computing "Network is the Computer", computing agents, distributed objects, and service oriented architectures, also failed by the wayside.