9 ms·
I'm assuming I'm not the only one who's afraid of Blink becoming the new Internet Explorer; instead of people following a web standard, they'll follow what's Ch
by tombert 8y ago
I'm assuming I'm not the only one who's afraid of Blink becoming the new Internet Explorer; instead of people following a web standard, they'll follow what's Chrome-compatible.
It's still better because Chromium is open-source, but I do worry that we're going to have a problem in the future with a lot of broken sites (YTMND-style).
- simonsarris 8y ago> instead of people following a web standard, they'll follow what's Chrome-compatible The browser vendors taking the lead over standards committees is how we got this far into HTML5, especially including Apple's/Safari's decision to ditch flash, and the WHATWG actually moving us forward vs the W3C. Unless Blink has a history or an expectation of deprecating serious functionality in the future, is it really so bad if websites follow what's Chrome-compatible instead of 'a web standard'?
- pas 8y agoW3C might be too slow, but eschewing at least a rough consensus and instead just ramming through whatever you feel like is the other extreme end of the spectrum. And Google is no saint, so if it benefits them and only them, who cares, Chrome will support it, the community be damned. And this - of course - applies to depreciation of functionality. (Think about any web feature/standard as another Google property, like G+ ... scary? But that's where we're headed with the Blink hegemony.)
- detaro 8y agoI don't think you can conclude from "things got better when browser vendors took over" that it'd be the same if there was one vendor dominating. They keep each other honest at least to a degree, forcing that issues are discussed and things thought out instead of someone in a browser team coming up with an idea and shipping it the first way they can come up with.
- mcgannon2007 8y agoBecause then any pull request introducing something into Chromium essentially becomes the web standard. For example, Google has a ton of influence on the project. If they want to, they can introduce something that benefits their services but eschews the web standard.
- holtalanm 8y agobut if Microsoft is moving to Blink, wouldn't they, as well, have (as you say) influence on the project? What, really, is a downside to having an open-source web engine that all browsers use? I'm failing to see one. The web would become less fragmented; the web standard would be (only slightly) irrelevant, and we would move forward without having to deal with browsers interpreting the spec/standard differently, which is what happens currently in a lot of cases.
- numbsafari 8y agoI generally agree with your sentiment on this. The only real downside I can think of is similar to the issues that motivated the renewed investment in OpenBGPD recently: that standards and ecosystems are made stronger when there is some level of competition and diversity. For example, a security bug in chromium becomes vastly more dangerous if everyone is working off that code. That said, hopefully there’ll be fewer of those because everyone is focused on the same codebase. The questions seem to be “how many browser engine implementations is truly necessary for a healthy ecosystem?” And “has the spec gotten so bad that it’s not feasible for the ecosystem to support a sufficient number of independent implementations?” Seems like <5, and maybe <3 is the answer to the first, and the answer to the second is we’ll see what happens to servo in 2019...
- bad_user 8y ago> but if Microsoft is moving to Blink, wouldn't they, as well, have (as you say) influence on the project? No. 1. Chrome will remain the dominant web browser 2. the Chromium repository itself is owned by Google The only leverage Microsoft is in forking Chromium, but that does nothing to Chrome's market. Google themselves forked WebKit when they couldn't get along with Apple. And that was back when Chrome wasn't as pervasive. So what makes you think Google would give a crap about Microsoft today?
- Yoric 8y agoThis is a good question. Let me give you an example. Let's imagine for instance that Google develops something called "Google Pay". Let's now imagine that WHATWG works on something called "WebPay". In a multiple-engines world, there would be pressure for Blink to support (and keep supporting) most major credit cards & payment mechanisms to let users pay using WebPay. In a single-engine world, one single manager at Google will have sufficient power to decide that WebPay supports only Google Pay. Feel free replace Google Pay and WebPay by any other technology strategic to Google.
- sureaboutthis 8y agoLet's not get confused. Blink is a rendering engine and not an API server.
- Yoric 8y agoThis kind of thing has stopped being true a long time ago. For all intents and purposes, web browsers are operating systems running web applications, taking care of security, etc. And all these Chromium-derived browsers are skins and utilities on top of Google's browser/OS.
- sureaboutthis 8y agoIt's still true and always will be. Blink is not a browser any more than the Linux kernel is a standalone operating system by itself with no attached software or applications.
- gsnedders 8y ago> The browser vendors taking the lead over standards committees is how we got this far into HTML5, especially including Apple's/Safari's decision to ditch flash, and the WHATWG actually moving us forward vs the W3C. That takes a somewhat limited in scope view as to what a web standard is; by most measures, what the WHATWG produces is as much a standard as anything the W3C does, and is certainly comparably useful to other implementers. > Unless Blink has a history or an expectation of deprecating serious functionality in the future, is it really so bad if websites follow what's Chrome-compatible instead of 'a web standard'? If someone wants to build a new web browser, can they do it without having to spend huge amounts of money on reverse-engineering Chrome and being bug compatible with it?
- danpalmer 8y ago> I'm assuming I'm not the only one who's afraid of Blink becoming the new Internet Explorer; instead of people following a web standard, they'll follow what's Chrome-compatible. This is already the norm. I use Safari and find many sites have issues. Before that I used Firefox and many sites had issues. Typically the JS works, but styling often looks different (and worse) on Safari and Firefox.
- idle_zealot 8y agoI run into the cause of this issue quite a bit when writing styling. The fact is that each major browser veers from the spec in its own unique ways, so if you're testing your page in a single browser (usually Chrome, though personally I use FF) the styling will often end up working differently in other browsers. As of now, the only real solution is to pick a set of "supported browsers" and to test your page in each of them before publishing, tweaking your styles to work around each engine's quirks. The problem with a browser monoculture is that it encourages developers to only test against the dominant platform, forcing competitors to be bug-compatible in order to provide a non-broken experience. The advantage is that a true and reliable standard would emerge, making developers' lives easier. Of course, the optimal solution would be for browsers to properly conform to the existing standards so that testing across browsers wouldn't be necessary in the first place, as any deviations would be a bug that would hopefully be fixed before too long.
- azinman2 8y agoDo you have examples? I use Safari and don’t find this to be true. Given Safari is what people use in iOS, id expect this to be rarely the case (most sites will test on an iPhone).
- ocfx 8y agoChrome will define the web standard instead of a slow moving and ancient committee.
- munificent 8y agoI think the bad state to be in is: * There is a number of implementations of the same platform. * Those implementations are competing and the market encourages them to be in-compatible with each other. You can avoid that bad state by having an explicit standard and applying pressure on all implementations to meet that standard. It usually comes at the expense of slower innovation. But another viable way to avoid that bad state is to simply not have competing implementations. A single canonical implementation also solves the problem of ensuring all users get a compatible experience. It can come at the expense of evolving in a way that doesn't meet user needs because there isn't a competitive incentive to win users. I don't think there are perfect solutions, but I also don't think it's the end of the world if this becomes a monoculture. There are tons of "platforms" that are effectively mono-cultures and seem to be OK. Every rechargeable tool company has its own battery pack form factor. Up until recently, each laptop company had a different port for the AC adapter. What I think this is really showing is that the market size of the web is shrinking relative to the size of the browser standards. Mobile apps have eaten up so much user share and HTML+CSS+JS+etc. has gotten so big and complex that the desktop web market can't effectively support multiple independent browser implementations any more. It's just too much work for too little return. There's maybe an interesting lesson here in not letting your platform get too complex. New features are always nice, but they have a cost. If you pile on too many of them, you may undermine your platform's ability to support multiple independent implementations.
- pcwalton 8y agoSo whether the Web can run on Rust-based parallel engine components should be beholden to the reporting structure at Google? Let's be clear: that is the future you are advocating.
- deleted 8y ago[deleted]
- cwyers 8y agoI mean, I don't know that I'm afraid of it, in the sense that it's clearly already been here for a few years now. Microsoft is one of the wealthiest companies on Earth and decided they didn't have the resources to compete with the web's Chromium monoculture.
- taf2 8y agoThis is not even close to comparable. I’ve said in other threads the issue with IE and really IE6 - was for multiple years Microsoft did zero development. The browser didn’t patch zero day exploits for months or even a whole year. Fundamentally IE6 was an extension of Windows via ActiveX controls. The layout bugs were permanent. Remember zoom:1, hack to fix a layout issue or just float:right etc... Blink is open source- you want to encourage innovation in the usability and utility of the browser and let people compete on market share of their browser product not how people’s web apps that run on that platform work or don’t work - The key is it’s open we’ll never have another IE6. Anyone can compile Blink. Look Microsoft is focusing on getting it to work on arm- cool. This is the opposite of locked to windoze only.
- paulie_a 8y agoI can't find any current stats in ie6 but the delay to upgrading was a pain point. While I wanted to just blacklist the browser from websites I was responsible for with a gigantic banner. I unfortunately didn't get that latitude. I just stopped caring if it worked or not for them. If a user complained I directed them their tech department. At a certain point I'm not supporting your internal outdated website because it requires an outdated browser.
- tssva 8y agoBlink already works on arm. Microsoft is working on getting it to work on the arm version of Windows.
- threatofrain 8y agoDon't people follow standards-compliant HTML/CSS/JS and compile to the browser of their choice? How often does a standards-compliant site work on Chrome but not on Firefox, assuming that all the targeted features you want are there?
- gbear605 8y agoIn reality, none of the browsers are quite standards compliant, and developers don’t know the standards by heart, so they often go with what works on their setup, which usually means Chrome.
- sureaboutthis 8y agoAny self-respecting and experienced developer who is worth his salt writes his code towards the standards and not toward a browser. If one needs to adjust his code because it doesn't work in a particular browser, then he's adjusting for the browser, not the standard.
- pjmlp 8y agoGiven the amount of devs that mix gcc or Linux for what ISO C or POSIX actually are, I would say the situation is not much different on the Web.
- ksec 8y agoI am starting to think we need an additional layer that compiles to HTML and CSS, and guarantee to work across all the browsers.