Also WASM doesn't look very mature to me, and chrome and apple can decide to stop supporting it if they want.
I'm also curious how well WASM works on mobile. I wish WASM could replace mobile apps somehow.
Also WASM doesn't look very mature to me, and chrome and apple can decide to stop supporting it if they want.
I'm also curious how well WASM works on mobile. I wish WASM could replace mobile apps somehow.
Can Apple ever switch back? Since their valuation depends on their income from the app store, they are forced to continue their policy.
However, is this a valid long-term strategy? Right now, most apps are by requirement single-purpose tools. Is Apple prepared for the time when there are user-generated apps? Much of what web3.0 can be is inhibited if Apple puts a tax on every transaction and prevents apps that change their source code.
Since the US mobile phone market is dominated by Apple, does this give China a huge advantage for developing the next generation of software?
[1] https://9to5mac.com/2011/10/21/jobs-original-vision-for-the-...
In fairness there's been some very exciting development on that front, mainly pushed by Fastly with their own compute @ edge proposal and opensourcing a set of tools like cranelift.
I think their use case of cloud fonction @ edge is absolutely perfect for webassembly on the server, and I'm actually impressed.
I agree the technology needs to mature a bit more. We need broader langage support, and then we'll have a very powerful and exciting tool to add to our tool-belt.
The author is saying that you will be able to replace docker (I think comparing to kubernetes is wrong) with wasm, because it can run code sandboxed.
Another example is a plugin ecosystem using wasm. Your go program would be able to load plugins written in c, lua or any other language that compiles to wasm.