| ▲ | charcircuit 8 hours ago |
| >long term browser compatibility Making a new browser engine hurts browser compatibility more than it helps it. It now becomes one more target that needs to be tested against, limitations need to be kept tracked of, etc. The best thing for long term browser compatibility is focusing resources into Blink. In regards to the standard we can use LLMs to cross reference the spec, with tests, and with the implementation to make sure all match. |
|
| ▲ | teekert 7 hours ago | parent | next [-] |
| Ah, you must be too young to have experienced early Internet Explorer, which attempted just this. |
| |
| ▲ | charcircuit 6 hours ago | parent [-] | | Internet Explorer was not open source acting as engine everyone's browser could use and it got abandoned by Microsoft. It is not the same situation. | | |
| ▲ | teekert 6 hours ago | parent | next [-] | | One could argue that effectively Blink is also not open source. At any rate users don't have power over it, as witnessed by the manifest v3 stuff jammed down our throats. | | |
| ▲ | pygy_ 2 hours ago | parent [-] | | Churn makes it impossible to keep up a fork, Google weaponizes its manpower, making the "open source" argument moot. | | |
| ▲ | charcircuit 31 minutes ago | parent [-] | | There are many active forks that are an existence proof that it's possible. It's also a ton of man power to maintain your own browser engine. |
|
| |
| ▲ | le-mark 5 hours ago | parent | prev [-] | | Monocultures are bad full stop. Blink is corporate controlled open source, which has been clearly less than. |
|
|
|
| ▲ | embedding-shape 7 hours ago | parent | prev | next [-] |
| > The best thing for long term browser compatibility is focusing resources into Blink. Lol, for Blink perhaps, what about the rest of the ecosystem, the web and the users, like the ones who don't even use Blink? Very idealistic point-of-view with no basis in reality, sadly, because wouldn't it be nice if we could care about just one engine? |
|
| ▲ | latexr 7 hours ago | parent | prev | next [-] |
| > The best thing for long term browser compatibility is focusing resources into Blink. That’s what makes Google more dominant, and if you think that’s a good idea you should really put down your LLM and go read up on a bit of history. Do you want to live in a world where a single company controls your access to the web? Are you eager to navigate through ad pages with a little bit of web? To have even more of your data mined? Browser diversity may be a bit annoying for developers, but it is good for users, and developers are users too. When there’s a lack of diversity, everyone but the dominant player is squeezed. |
| |
| ▲ | charcircuit 6 hours ago | parent [-] | | Google's dominance comes from market share not from owning upstream. If a different fork took 90% market share that fork would have the dominance and power. | | |
| ▲ | samus 5 hours ago | parent | next [-] | | And that market share is maintained by integration with Android and low-key sabotage of others browsers, especially Firefox. Similar to how Microsoft maintained its monopoly decades ago. | | |
| ▲ | charcircuit 28 minutes ago | parent [-] | | Whether a new browser uses a brand new engine or not that doesn't stop Chrome being integrated with Android. |
| |
| ▲ | latexr 2 hours ago | parent | prev [-] | | > If a different fork took 90% That can only happen if we don’t all focus resources on Blink, which is the point. By definition, we can only have other engines if diversity is a thing. The problem isn’t specifically Google (though they are a problem), but any one individual company having all the power. | | |
| ▲ | charcircuit 24 minutes ago | parent [-] | | >That can only happen if we don’t all focus resources on Blink Why? What's fundamentally stopping Edge market share from going to 90% that would go away if they switched back to their own browser engine? >but any one individual company having all the power. Open source means that anyone can make any change at any time. Google doesn't have all the power over what a fork does. A fork is still in full control. |
|
|
|
|
| ▲ | Oxodao 7 hours ago | parent | prev [-] |
| yeah in a perfect world google dictates how the standard will evolve, we kill all competition so we're sure that you have only one target to build your software against, I'm sure a monopoly will greatly improves innovation and not be used to stiffen competition. /s |
| |
| ▲ | charcircuit 6 hours ago | parent [-] | | Using Blink doesn't mean you have to defer all decisions to Google. You just benefit from not having to duplicate work. | | |
| ▲ | kryptiskt 3 hours ago | parent | next [-] | | And you can't do what Google doesn't want you to do. That's a nice ad blocker you have there, shame if we removed support for it. | | |
| ▲ | armadyl 10 minutes ago | parent | next [-] | | “The benefit of open source is that anyone can fork and modify the code!” Yet somehow this argument seems to evaporate since people’s brains short circuit the moment they see the name Google. The community can always fork and maintain a separate version of Chromium if necessary. Or does this concept only not apply to Chromium? | |
| ▲ | charcircuit 30 minutes ago | parent | prev [-] | | Brave literally ads an ad blocker into the browser itself. When you fork software you can do whatever you want to it. |
| |
| ▲ | samus 5 hours ago | parent | prev [-] | | Except one does since Google is the primary maintainer. Anyway, work on other browser engines is not duplicated or wasted. | | |
| ▲ | charcircuit 22 minutes ago | parent [-] | | It's easier maintaining a fork of Blink than an entirely different engine. Google being the primary maintainer doesn't mean that browsers can't make large forks. >work on other browser engines is not duplicated or wasted. How is having N engine developers implement some new addition to the EMCAScript or CSS standard for each of their engines not duplicated work? |
|
|
|