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

All of the environments you describe there sound to me like they would benefit from web apps that become responsive after an initial page load of less than 100KB, followed by ~10KB round trips to the server to fetch additional data.

As opposed to the >2MB initial page loads that have become so common with heavy React SPAs in exchange for the theoretical benefits of avoiding more page loads for further interactions.



They benefit from a .exe (or a .tar.gz or a .apk) downloaded when convenient and run locally


Any app with dynamic data would still need to make some sort of HTTP request before rendering some view with that new data. I don’t really get your point.


If the data is also local, which it can be and in many cases should be, there’s no network request round trip.




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

Search: