Hacker News new | past | comments | ask | show | jobs | submit login

That's unnecessary. I ship my apps as single-file executables that are ready to go. In the worst case you can use a directory like zoom does (on Linux at least) which contains all the libraries and dependencies you need.



Thats still way more awkward than what the web provides.

- I don't need to uninstall / delete a website when I'm done with it

- I don't need to pick an executable format. (Portable or installed? windows mac or linux? dpkg or rpm? From the dev's website or through homebrew/apt? Is a portable executable even available for this application?)

- I don't need to give the author of the webpage access to all my local files.

Native programs are also often 10x+ as large as websites. (Eg the facebook iOS app is somehow 488mb)

These problems are all solvable. Wasm alone will go a long way to solving the sandboxing and app format problems. But we still need to build the platform, whatever it is.


The facebook website managed to eat 1GB of ram alone multiple times.


Right! And despite that, it loads in seconds. Traction would be very different if people had to install facebook on their computers to try it out!

"Oh yeah its this cool social network.. just download - no, not the portable executable version... yeah, its 300 megs... Then you need to click it to install it"


Seconds? It can be minutes depending on where one is located on the globe.

Not everyone is luckily at home using broadband connections with flat rate.


Sure; but people without a broadband connection will have even more trouble with an installed application. They're pretty consistently bigger.


Native applications can be distributed by other means, and keep being installed after the owning company is long gone.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: