5 ms·
... if you only do it once.
by tjoff 2y ago
... if you only do it once.
- dymk 2y agoOkay, for the sake of the argument, let's assume at some point you amortize the fixed costs of native compilation down to zero. Tell me how running a native binary is inherently easier than opening a webpage?
- marcodiego 2y agoTo open a webpage you have first to run a native binary. So, running a native binary is necessarily easier than opening a webpage.
- dymk 2y agoYou are confusing "Number of steps" with "Easy". They're also the same number of steps. If I tell my OS to open an `html` file, it opens a browser window.
- marcodiego 2y agoIf doing task B requires doing task A first, then doing task A is necessarily easier than doing task B.
- strawhatguy 2y agoI think you're confusing "simple" and "easy". One task vs two is simpler, yes.
- deleted 2y ago[deleted]
- tjoff 2y agoThe performance and user experience of a native binary is on a whole other level.
- dymk 2y agoIt's really not with wasm. Sure, there is a performance difference. It is not a "whole other level".
- tjoff 2y agoThe user experience is still on a whole other level, not living inside the browser. And the number of times I've used a wasm app, more than once, that actually had some theft do it. Well, I can't think of a single one. So, we will see how well it does in practice. Wasm is great, but if the goal is to move native applications do the webb it isn't something I look forward to.
- chrsig 2y agowhich is actually pretty often for a demo!