3 ms·
Would you say premature standardization is a part of the problem? It seems marginally better that Google at least asks others in an open forum. Microsoft basic
by paulryanrogers 6y ago
Would you say premature standardization is a part of the problem?
It seems marginally better that Google at least asks others in an open forum. Microsoft basically dictated defacto standards by leveraging their dominant OS.
My preference is for vendor prefix like namespacing and waiting for at least two independent implementations before any serious standardization. But for web dev on the cutting edge I can see the temptation to play with new toys.
- btrask 6y ago> Would you say premature standardization is a part of the problem? More than that. It's a joke to try to standardize something that is still an open research problem. If something is going to be a standard, there should be at least one off-the-shelf algorithm you can implement that is roughly on par with the competition. I'm not saying there shouldn't be any room for innovation, but... Well, maybe there just isn't. A standard probably has to be a lowest common denominator.
- pas 6y agoThe problem is that the browser market is not actually a direct market for browsers. People don't buy browsers. They buy OSes, computers, phones, tablets, cars, fridges and other devices that happen to have browsers in them. So the incentives are very skewed, the available resources too. Google will always out-compete Firefox in a relatively short time on whatever metric Mozilla comes up with. (If Google wants to of course. That's why Apple is doing all this privacy marketing thing and providing subpar but privacy-aware products.) Ideally the browser and the web ought to be unbundled. People who pay for the Internet access should have a voice in where the Web goes. The ISPs should transfer some money to browser vendors. Sounds crazy? Yes, but that would at least provide different market forces. (And maybe browser vendors should be prohibited from accepting any other sources of revenue. Okay, but what about pull requests? Yeah, good question, this was never an easy problem.)
- d1zzy 6y ago> waiting for at least two independent implementations before any serious standardization What's the time limit on that wait? Should a vendor wait years to get a feature through other implementations? Should product development be stuck on other parties (potentially competitors) implement the necessary features required to develop the product? Over time, this would result in a very large number of features limited to "vendor" namespace, how is that, in practice, different from having the features standardized (but largely unimplemented by other vendors)? And how is that better for users? What if the vendor wants to pay someone to get those features quickly into alternate open source implementations, wouldn't HN complain then that the vendor now has direct influence in the other product's development? It seems to me like given a set of requirements as simple as "quickly develop new web products that (may) require new web features" Google just can't win.