DEV Community

Discussion on: Why WebAssembly (WASM) is the Future of High-Performance Web Apps

Collapse
 
xwero profile image
david duymelinck

I just read dagger.io/blog/replaced-react-with-go.

I think the main problem with webassembly is that the code can be decompiled. A lot of companies want to keep their code secret.

Collapse
 
vibhuvibes profile image
Vaibhav thakur

That's a valid concern! WebAssembly, like JavaScript, can be decompiled, but so can most client-side code. While it’s not a perfect security solution, obfuscation and encryption techniques can make reverse engineering more difficult. For businesses needing true secrecy, sensitive logic should always be kept on the server. That said, WASM’s speed, portability, and language flexibility still make it a game-changer for performance-intensive web apps.

Collapse
 
plutonium239 profile image
plutonium239 • Edited

Wasm is only for client side stuff - server side you can already run whatever binary you want.

So, it is replacing client side javascript - which again can't be secret.

Collapse
 
vibhuvibes profile image
Vaibhav thakur

You're right that WASM primarily enhances client-side performance, but it's not just about replacing JavaScript. It enables running code-heavy applications (like Figma, AutoCAD, or even AI models) directly in the browser with near-native speed. Also, while it’s true that client-side code isn’t secret, WASM still offers advantages like obfuscation, better performance, and cross-language support. On the server side, projects like Wasmtime and wasmCloud are exploring its potential too! Thanks for your insights!

Thread Thread
 
plutonium239 profile image
plutonium239

You're replying to the wrong person I think.

Thread Thread
 
vibhuvibes profile image
Vaibhav thakur

Apologies for the mix-up!.πŸ™‡β€β™‚οΈ