4 ms·

and yet 20 years later, the situation is not that better ... each browser vendors is still fighting the other ones by adding features that make their browser t

by zwetan 10y ago

and yet 20 years later, the situation is not that better ... each browser vendors is still fighting the other ones by adding features that make their browser the platform of choice like chrome API only available for the chrome app store let's all kill Flash because plugins are bad, but let's not hesitate to add our own plugin, oh excuse me the politically correct word is "addon" as a native extension to cast things around. when CPU, RAM and bandwidth are no more an issues let's cache aggressively everything so that bloated browser does not feel so slow anymore.

newjersey 10y ago
Some context for people like me Google cast is built into chrome https://news.ycombinator.com/item?id=12383367 https://news.ycombinator.com/item?id=12383367
DaiPlusPlus 10y ago
Modern browser extensions are written in JavaScript, making them portable, verifiable, and easily sandboxed - not something you get with an executable binary blob that until very recently ran in the same permission context as the local user - which on Win9x through XP meant root. Handily (and amusingly), Microsoft's Edge extension API is designed to be compatible with Chrome's - I understand there's a degree of mutual-intelligibility with Firefix too. And aggressive caching just makes sense - consider people today with 10+ Chrome Windows open, all with 50+ tabs each - not even 10 years ago IE6 still ruled supreme - with one document per window. And even then machines had similar orders-of-magnitude of RAM as they do today - my 2006 rig had 4GB of RAM (XPx64) my current machine has 4 times that.
- nilved 10y ago
  > Modern browser extensions are written in JavaScript, making them portable, verifiable, and easily sandboxed - not something you get with an executable binary blob that until very recently ran in the same permission context as the local user - which on Win9x through XP meant root. Do you think this means that browser extensions are secure in the least?

by zwetan 10y ago

newjersey 10y ago

Some context for people like me Google cast is built into chrome https://news.ycombinator.com/item?id=12383367 https://news.ycombinator.com/item?id=12383367

DaiPlusPlus 10y ago

Modern browser extensions are written in JavaScript, making them portable, verifiable, and easily sandboxed - not something you get with an executable binary blob that until very recently ran in the same permission context as the local user - which on Win9x through XP meant root. Handily (and amusingly), Microsoft's Edge extension API is designed to be compatible with Chrome's - I understand there's a degree of mutual-intelligibility with Firefix too. And aggressive caching just makes sense - consider people today with 10+ Chrome Windows open, all with 50+ tabs each - not even 10 years ago IE6 still ruled supreme - with one document per window. And even then machines had similar orders-of-magnitude of RAM as they do today - my 2006 rig had 4GB of RAM (XPx64) my current machine has 4 times that.

nilved 10y ago
> Modern browser extensions are written in JavaScript, making them portable, verifiable, and easily sandboxed - not something you get with an executable binary blob that until very recently ran in the same permission context as the local user - which on Win9x through XP meant root. Do you think this means that browser extensions are secure in the least?