Live data from Hacker News

Not So Fast: Analyzing the Performance of WebAssembly vs. Native Code

usenix.org

211–212 of 212 posts

Re: Not So Fast: Analyzing the Performance of WebAssembly vs. Native Code

#211
post #207

Earlier quoted context omitted.

I fail to see the point. Either the developers are able to use the tooling at their disposal to deliver awesome products or not. Skype was originally coded in Delphi, so yeah.

If you think Skype’s user experience was ever in any way “good”... what do you consider “bad”?

Yes, Skype UX was great before MS acquisition and rewrite into React Native.

Anything written with Electron is pretty much bad.

I only put up with Slack and VSCode due to job requirements.

Re: Not So Fast: Analyzing the Performance of WebAssembly vs. Native Code

#212
post #147

So many comments here missing the point. As a developer, I can use wasm to ship a single binary that works on Windows, Mac, Linux, Android, and iOS. I can use the language that I want. I don't need to have Xcode, visual studio, android studio, or any other set of tools: you can reasonably build an app with your text editor and LLVM. And then, you can use my app by typing its address into your address bar. No installa…

> So many comments here missing the point. As a developer, I can use wasm to ship a single binary that works on Windows, Mac, Linux, Android, and iOS. But we've accomplished that by effectively turning web browsers into VM's that have a complexity on par with a full operating system. I have a sneaking suspicion that we're going to end up deciding that was a huge mistake.

Web browsers are where it starts but we're getting native WASM runtime/containers that can just start a program from the disk. The browser then just becomes a shell around it with the ability to find a binary over a URL rather than locally, along with some other web-related features.
Post reply on HN