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

> open standards also slow down the development of new features

On one hand, that is not right: open standards mean no walled garden, rather than each garden equally ugly.

On the other hand, that is exactly the point: no new feature can be used to buy the users' freedom to interact with customers of other services.



> On the other hand, that is exactly the point: no new feature can be used to buy the users' freedom to interact with customers of other services

so the point is a degraded experience? how can that be the point?


Would you like to go back to the dark times of IE6?


All the browsers since IE6 are built on open standards. It was stagnation and lack of openness (ActiveX) which caused IE6 to hang around so long.


ActiveX was relatively open-ish. Back in the days young me used a Visual Studio 6 off of eDonkey to develop applets in VB6.

The problems were that:

- unlike modern compiled code for the web - WASM and transpiled JavaScript - Java and ActiveX got executed with host privileges which made both an incredible entry point for malware such as "dialers" and early viruses.

- many corporations and governments (e.g. Korea [1]) built their stuff in ActiveX or mandated its use in actual laws and regulations, while only MS Internet Explorer ever implemented ActiveX out of said security reasons.

- many corporations and governments only ever coded and tested against IE6 which meant that their sites and products were dependent on IE6-specific quirks

[1] https://www.forbes.com/sites/elaineramirez/2016/11/30/south-...


Are you arguing with yourself?




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: