3 ms·

You're implying that nobody in particular controls WebKit? That is patently false. And the distinction between a browser engine monopoly and a browser monopoly

by ootachi 15y ago

You're implying that nobody in particular controls WebKit? That is patently false. And the distinction between a browser engine monopoly and a browser monopoly is irrelevant to this discussion. We're talking about browser engines here. Furthermore, suggesting that people can add "new rendering features and options" on top of WebKit solves nothing! Those would just have to be prefixed in the same way, or would be incompatible, and we're back to square one.

batista 15y ago
You're implying that nobody in particular controls WebKit? That is patently false. "When you assume", well, you know the rest... I only say that neither Apple nor Google (or Amazon, Samsung, QT, KDE, etc) control Webkit now. If all of them control it, thats not a monopoly of control. Plus, it's open source. If you want to toil at it for free, or throw millions of money to take it to the direction you want, you are able to. And the distinction between a browser engine monopoly and a browser monopoly is irrelevant to this discussion. We're talking about browser engines here. We're talking about innovation re: browsers, in this particular THREAD (threads can diverge from the main post point, and such innovation can also happen at the browser level. Plus, I ALSO covered the engine monopoly with respect to browser rendering innovation. Furthermore, suggesting that people can add "new rendering features and options" on top of WebKit solves nothing! Those would just have to be prefixed in the same way, or would be incompatible, and we're back to square one. Only I didn't say this AS a solution to the prefixing issue --which I didn't address at all. What I addressed was that a "single browser engine" != "rendering innovation stops", because innovation can happen ON TOP of a single browser engine as well as on top of different engines.

by ootachi 15y ago

batista 15y ago

You're implying that nobody in particular controls WebKit? That is patently false. "When you assume", well, you know the rest... I only say that neither Apple nor Google (or Amazon, Samsung, QT, KDE, etc) control Webkit now. If all of them control it, thats not a monopoly of control. Plus, it's open source. If you want to toil at it for free, or throw millions of money to take it to the direction you want, you are able to. And the distinction between a browser engine monopoly and a browser monopoly is irrelevant to this discussion. We're talking about browser engines here. We're talking about innovation re: browsers, in this particular THREAD (threads can diverge from the main post point, and such innovation can also happen at the browser level. Plus, I ALSO covered the engine monopoly with respect to browser rendering innovation. Furthermore, suggesting that people can add "new rendering features and options" on top of WebKit solves nothing! Those would just have to be prefixed in the same way, or would be incompatible, and we're back to square one. Only I didn't say this AS a solution to the prefixing issue --which I didn't address at all. What I addressed was that a "single browser engine" != "rendering innovation stops", because innovation can happen ON TOP of a single browser engine as well as on top of different engines.