6 ms·
OP here. It's hard to make the case internally to switch to an orchestration platform that works for "most of our apps". Of course, it's similarly hard to make
by throwaway894345 6y ago
OP here. It's hard to make the case internally to switch to an orchestration platform that works for "most of our apps".
Of course, it's similarly hard to make the case for WASM, which is similarly incomplete today; however, there appears to be mutual interest from language communities and the WASM team to get support working. Even still, I don't intend to make the case until WASM has a decent track record of supporting those languages. But I have more optimism that WASM will get there than JVM or CLI.
Note also that while "JVM and CLI have support for those languages", their support for Python (and probably JavaScript) is only nominal. You can't reasonably use Jython or IronPython with the rest of the Python ecosystem, but WASM at least has a plausible path forward. I also strongly suspect that support for sandbox execution of the other languages is similarly nominal--if it's technically possible, I'd be surprised if anyone is doing this in practice.
- pjmlp 6y agoI advise you to watch these talks, "Why the #wasmsummit Website isn't written in Wasm" https://www.youtube.com/watch?v=J5Rs9oG3FdI https://www.youtube.com/watch?v=J5Rs9oG3FdI "Production Ready Server-Side WebAssembly: The Challenging Parts" https://youtu.be/-4zNzxqUBsk?t=3155 https://youtu.be/-4zNzxqUBsk?t=3155