Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

some of the compute workload still needs to be on a backend because of security concerns. if you offload too much stuff on a client-side, then any hacker can mess with it and break your system.

for example you can get angular debugger extension for chrome and mess with any online shop that uses this system to "adjust prices" for your cart during checkout



This is only a problem for online services, multiplayer games etc. These shouldn't trust client-provided data, including data that comes from WASM. But there are countless applications that can be entirely local, with no need to interact with any sort of "cloud" services. WASM can potentially be quite helpful there


Parent meant WASM on the server.


the backend could compile to wasm as well.


and what is the profit in compiling C/C++/Rust into wasm, instead of native binary code?


Better hosting/deploying/debugging/etc because WASM can be hot-loaded and easily embeddable.

e.g. https://www.cloudflare.com/products/cloudflare-workers/


well this thread was about wasm vs java, but...

advantages: sandbox, portability

disadvantages: performance, platform integration

nobody's saying that server-side wasm will be universally the right choice.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: