Live data from Hacker News

Browsers

adactio.com

61–70 of 316 posts

Re: Browsers

#61

I feel like I’m missing something, because I keep seeing blog posts that tell me a browser monoculture is bad (and the irony of Microsoft saying this is nearly too much), but none of them tell me why. I understand that it was bad in the IE6 days, but IE6 was also closed source and could only be run on Windows (see also the irony of Microsoft discontinuing IE on Mac, not wanting to compete with Safari, a browser made…

Please read this different take and explanation in this article linked within the main article, titled "The ecological impact of browser diversity", by Rachel Nabors. [1]

[1]: https://css-tricks.com/the-ecological-impact-of-browser-dive...

Re: Browsers

#62
post #12

Sometimes I still browse Digg (it's different now). Since the last Firefox update from a week ago which disabled Symantec certificates the site doesn't work anymore. I bet the day Chrome disables Symantec certificates they will immediately notice and fix it. It's sad that in one week not even one of their people opened it in Firefox, and not many of their users either (there was just a couple of mentions on Twitter a…

Chrome also shows an error. The reason nobody at Digg noticed is that Digg is not https by default, so only people using certain extensions would hit that error.

Re: Browsers

#63

I feel like I’m missing something, because I keep seeing blog posts that tell me a browser monoculture is bad (and the irony of Microsoft saying this is nearly too much), but none of them tell me why. I understand that it was bad in the IE6 days, but IE6 was also closed source and could only be run on Windows (see also the irony of Microsoft discontinuing IE on Mac, not wanting to compete with Safari, a browser made…

Seems like you have yourself answered your question in your list line. One browser owned by one organization could hijack whole internet for its own interests. Just like in any other necessary item we need multiple supple options are good for creating healthy competition.

Re: Browsers

#64
There are several comments on this post wondering why a browser monoculture is bad or speculating that a browser engine monopoly is inevitable and ought to be accepted.

Let's just replace 'browser' with OS (ironically the similarities are becoming more with each passing day) above... would we still say the same? Is an OS monoculture good, regardless of whether it is inevitable? Have we forgotten the power that MS had with Windows during the 90s and early 2000s before Linux, MacOS and Android became viable alternatives?

Given that browsers are becoming the new OS and VM, we need competition in this space more than ever, going forward. Let's not accept Chrome/Google as the One Ring.

Re: Browsers

#65

I feel like I’m missing something, because I keep seeing blog posts that tell me a browser monoculture is bad (and the irony of Microsoft saying this is nearly too much), but none of them tell me why. I understand that it was bad in the IE6 days, but IE6 was also closed source and could only be run on Windows (see also the irony of Microsoft discontinuing IE on Mac, not wanting to compete with Safari, a browser made…

I completely agree. I think there is a bit of unjustified fear here given that Edge's ridiculously small installed base had absolutely no affect on the browser mono-culture anyway. Most developers did not go out of their way to test in Edge.

This is really no different than the Linux Kernel. People will take KHTML, Webkit, Blink, V8, JavaScriptCore and remix those into dozens of different products all with better web compatibility than something home grown from Microsoft with no chance of adoption.

Re: Browsers

#66

This move by Microsoft may probably help Microsoft have Windows users using its browser, but I seriously doubt if it's good for the web. There are people claiming that Microsoft could easily fork from Chromium, but honestly, do you see that happening in the next few years? Having read that Microsoft's Edge team was a very small one, I don't believe Microsoft will fork Chromium anytime in the next two or three years (…

So the only competitor to Google’s monopoly on web browsers is... funded almost entirely by Google? Yikes

While Safari’s desktop market share is minimal and it really only competes with Chrome directly on Macs. No one is going to use Chrome only features that don’t work on iPhones.

Re: Browsers

#67

I feel like I’m missing something, because I keep seeing blog posts that tell me a browser monoculture is bad (and the irony of Microsoft saying this is nearly too much), but none of them tell me why. I understand that it was bad in the IE6 days, but IE6 was also closed source and could only be run on Windows (see also the irony of Microsoft discontinuing IE on Mac, not wanting to compete with Safari, a browser made…

IE, at its height, was available outside windows. https://en.m.wikipedia.org/wiki/Internet_Explorer_for_Mac At that time, 2001-2002, IE6 was highly praised. You don’t get to 96% marketshare by being something everybody hates. The hate came later when CSS demand ramped up and it became clear IE6 used a non-standard box model. Worse still MS essentially abandoned the browser, the result of total marketshare dominance,…

> IE6 used a non-standard box model.

Which we all use now anyway because it was right way to do it...

    * {
      box-sizing: border-box;
    }

Re: Browsers

#68
post #4

Honestly I just see all this, even despite the author claiming taking time to "mull it over", as a knee-jerk reaction. There is little evidence that MS changing to Blink/V8 will have any tangible impact on the web. Microsoft has hardly offered much as far as competition and diversity goes since IE6, basically the only web "innovations" they're responsible for is a bunch of IE-specific APIs that didn't work in any oth…

[deleted]

Re: Browsers

#69

I feel like I’m missing something, because I keep seeing blog posts that tell me a browser monoculture is bad (and the irony of Microsoft saying this is nearly too much), but none of them tell me why. I understand that it was bad in the IE6 days, but IE6 was also closed source and could only be run on Windows (see also the irony of Microsoft discontinuing IE on Mac, not wanting to compete with Safari, a browser made…

I think we first need to agree that competition in a general sense—that is including browsers and everything beyond—is a good thing. It's healthy for any market to have viable competitors; principally for the consumers, but also for the vendors (so that they do not stagnate). If we don't agree that competition is healthy, then I don't believe it's possible to agree on the second-order matters.

There are several second-order reasons why a monoculture is damaging for the browser industry. I will give a few examples:

1. A monoculture encourages web developers to test on a single platform with the assumption that all other platforms, and even industry standards, are meaningless. Many of us are web developers, and most of us are guilty of dismissing low-share platforms during testing. But as long as some viable competitors exist, we nominally target the industry standards in the hope that by doing so, the platforms we do not test on will have a modest/tolerable (maybe even good) experience.

2. A monoculture is self-reinforcing. Losing established viable competitors makes it more difficult for new competitors to enter the market. If we allow second-tier browsers to be rendered meaningless, we all but ensure a long and (eventually) painful stagnation, and create an ever-larger hurdle for a new entrant to clear to reach any significance (as more an more of the web is designed to work with a single platform). While it may sound passably agreeable to have a Chrome monoculture in 2019, do we want to still have a Chrome monoculture in 2029? For my part, I hope we see an increasing set of options in most areas of life over time, even in "browsing," whatever that ends up looking like in 10 years.

3. We don't know what future stagnation will look like. We don't know what opportunities we will have lost by making it more difficult to compete or by losing the healthy diversifying force of competition. It's a classic problem of the unseen. Projecting forward, we predict testing will be a bit simplified, but we cannot know what innovations we'll never see (or won't see as quickly) because the hurdles for experimentation were too high. Today, if Firefox introduces a new feature, even though its usage is relatively small the usage is still large enough in absolute terms that the innovation isn't entirely under the radar for most of us. If Firefox's share were 0.8% instead of 8%, far fewer of us would even notice if they added a slick new feature, leaving the feature unheralded and obscure despite its potential wide appeal.

Re: Browsers

#70

There are several comments on this post wondering why a browser monoculture is bad or speculating that a browser engine monopoly is inevitable and ought to be accepted. Let's just replace 'browser' with OS (ironically the similarities are becoming more with each passing day) above... would we still say the same? Is an OS monoculture good, regardless of whether it is inevitable? Have we forgotten the power that MS had…

Unfortunately that's not really a valid comparison at all. Browsers all try to stay compatible with each other. OSes do not in any way try to stay compatible with each other. Programming apps for Linux, Mac, and Windows requires entirely different code. Programming for Firefox, Chrome, Edge, Safari do not (or at least not supposed to unless you're used new APIs or edge cases)

You can't currently make an alternative browser in the same sense that you can make an alternative OS. An alternative browser would not use HTML, CSS, JavaScript. It would use something else in the same way that MacOS/iOS push ObjectiveC and Swift where as Android pushes Java/Kotlin and other OSes other languages and each OS as it's own UI API

Post reply on HN