3 ms·

IE6 was basically the canary in the coalmine. Holding the web back from constant change was a good thing as it let many more implementations be usable. Remember

IE6 was basically the canary in the coalmine. Holding the web back from constant change was a good thing as it let many more implementations be usable. Remember Opera and the various other browsers around at the time? Not long after IE6 died, they got crushed too by Google using change as a weapon against its competitors. The recent notable change of Google requiring JS even for its own search engine, and thereby shutting out simple and basic browsers like Lynx, should be extremely concerning for the future of the web.

greiskul 1y ago
The reason Microsoft held the web back is because it saw it has a potential threat to it's dominance as the main platform for applications. And if you are actually concerned about the future of the web, instead of it's past, I would more concerned with Apple holding back development on Safari, to make people focus on writing native apps for mobile. There are so many apps that in the past would be websites, but end up being natively coded because that's the only way to get a good customer experience in mobile.
- 1718627440 1y ago
  > And if you are actually concerned about the future of the web >I would more concerned with Apple holding back development on Safari I think they are more concerned with the future of the web due to Google and so am I.
- hbn 1y ago
  You're worried about Safari in the browser space? It's the only browser that's holding back a near 100% monopoly from Google at the moment. If Apple gets forced to allow other browser engines on iOS, it's game over. Google wins the web forever.
bapak 1y ago
The HTML-only web has been dead for years. Documents may be safe, but publishing websites that work without JS is war with no winners.
hbn 1y ago
> Google requiring JS even for its own search engine This has been annoying me personally because sometimes I'll "bookmark" something I want to come back to like a movie or a video game by Googling it and leaving the tab open on my phone's browser. But now, seemingly when those pages are suspended, Javascript isn't allowed to run in them, so all my Google search tab thumbnails are just a static screen telling me that I need to enable Javascript.

greiskul 1y ago

The reason Microsoft held the web back is because it saw it has a potential threat to it's dominance as the main platform for applications. And if you are actually concerned about the future of the web, instead of it's past, I would more concerned with Apple holding back development on Safari, to make people focus on writing native apps for mobile. There are so many apps that in the past would be websites, but end up being natively coded because that's the only way to get a good customer experience in mobile.

1718627440 1y ago
> And if you are actually concerned about the future of the web >I would more concerned with Apple holding back development on Safari I think they are more concerned with the future of the web due to Google and so am I.
hbn 1y ago
You're worried about Safari in the browser space? It's the only browser that's holding back a near 100% monopoly from Google at the moment. If Apple gets forced to allow other browser engines on iOS, it's game over. Google wins the web forever.

bapak 1y ago

The HTML-only web has been dead for years. Documents may be safe, but publishing websites that work without JS is war with no winners.

hbn 1y ago

> Google requiring JS even for its own search engine This has been annoying me personally because sometimes I'll "bookmark" something I want to come back to like a movie or a video game by Googling it and leaving the tab open on my phone's browser. But now, seemingly when those pages are suspended, Javascript isn't allowed to run in them, so all my Google search tab thumbnails are just a static screen telling me that I need to enable Javascript.