I don't understand why you thought i was talking about bringing them benefits, but since you brought it up, I often donate to projects I use and do extensive testing on git branches on nearly all the software I can.
but regardless, I wasn't implying that it would benefit them at all.
well, it would be nice if they added some more features to the app since its pretty bare bones. Otherwise I dont see myself migrating to this.
I am quite disappointed at the lack of transparency regarding this.
this is from the google research team, they contribute a LOT to many foss projects. Google is not a monolith, each team is made of often very different folk, who have very different goals
Boring hit piece that way overblows some issues on the topic.
this is quite frankly, a really dumb picture that is wrong on many accounts
uses the GNOME interface
yeah thats a no from me.
The reason why firefox and chrome work so well, is that they literally have been in development for over a decade. In Firefox's case, it's actually over two decades now.
Instead of trying to reinvent the wheel, why not support some currently existing alternative browsers that look promising? You have servo, you have webkit, and you even have a ladybird now. That's three potential browsers.
All three are under somewhat active development. Servo, in my opinion, looking the most promising, that shares a lot of dependencies with Firefox still, which means maintenance cost is not super high. It's easy to hack on, and of course it's rust. ~~who doesnt love rust~~
sounds like a lot of work when you could just install arch or nobara and be done with it
literally, all Chrome OS / chromium OS needs to do for me to actually embrace it. is native out of box flatpack support
one issue I might see them having with flatpack, is the permissions right now are handled kind of stupidly IMO. but if those get solved I think flatpack would be a great addition to chromium os ecosystem
all chromeOS needs to be immensely more useful is flatpak support, if chrome OS supported flatpaks directly, it could very well be my goto (well not chromeOS directly, probably thoriumOS) for older linux PCs for general populace
None of it is "that bad". However its understandable if contributors want to separate out and have a more open governance.
As long as they keep the licenses open where both projects can pick and choose. Some forks do so "maliciously" and change licenses to prevent upstream from pulling changes back.