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

Beyond managing your identity/s, the most compelling notion this brings to my mind is that sites should reduce transmission of redundant data: You specify the structure once then only the data is transmitted (what someone else referred to as "like iOS apps"). To an extent we are already moving in this direction with asynchronous update technologies, but rather than a next-gen browser, it seems like we need a next-gen language that places a primary emphasis on reducing wasteful transmission of redundant information. E.g., On iOS I update my FB app when there is a change to its structure and then I do so exactly once; Why am I re-downloading its structure in my browser window multiple times a day?



This is exactly what I'm planning, and have wrote about in my follow-up post: http://ashraful.org/browser-features/

In particular, you can install these native apps and no longer need to download the UI again and again, instead just get the updated data. And access the past data even when you're offline.


Do those extra 20 kilobytes really matter though? In the age of gigabyte streaming video, who cares if you redownload facebook's UI a few times a day?


Sure the relative lost efficiency from that extra 20kb may be


may be minor compared to other use, but I bet it accounts for a fair proportion of the time to page render.




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

Search: