webkit and blink are two massively different beasts, webkit and blink is just an engine in the end, the stuff on top matters too. If it was as simple as engines, it would be like comparing gnome web to chromium.

why? what does country of origin have to do with it in general?

Chrome and firefox on android use their own image decoders.

I don’t think it would be that bad. Users have proven willing to eat whatever trash chrome shoves down their throat. Firefox has also proven that they don’t really do a great job at preventing chrome from controlling the web market as shown with JXL. They completely dropped the ball here and only recently after safari has proven to successfully adopt it, choosen to follow suite.

Apple has turned out to “prevent the chrome monopoly” far more effectively then firefox has.

Personally I hope firefox dies as fast as possible so we see some focus on good alternatives.

Gecko is not a good platform, there is a reason why people who use geckoview eventually all migrate away from it, the most recent example I can think of is wolvic, which hasn’t replaced geckoview yet, but does have the version 1.0 of a chromium release now.

The sooner we get real alternatives to chromium and stop pretending that gecko is one the better. Currently servo is progressing really fast, has good APIs and usability for both a full desktop browser and embedded usecases (but still very immature).

in general, an application can allow you to log in to do things like like and comment, but most applications choose to instead. Comments might be a bit more tricky, but applications like smart tube next support liking and disliking.

It could also be possible to do what grayjay does, and simply open a webview for the video in question

skia doesn’t actually have that many alternatives, and skia is well maintained used by a large amount of projects. and none I am aware of are nearly as mature as skia is.

Honestly, I’m not sure that’s quite a good takeaway. The article itself was pretty much a bland nothing burger and the articles that were cited were, again, pretty bland. The biggest thing I can find is that they won’t be facing off another browser and then it’s like, well duh.

It’s just one of those things. It just feels like the original dude said one thing and the author interpreted it a completely different way.

saying ‘no code’ from rivals seems highly misleading, and I can’t seem to see a hard citation for this, in fact, it very directly contradicts this same sentence from the article

He also said that unlike SerenityOS, Ladybird will “leverage the greater OSS ecosystem,” meaning that it will use other open source libraries for some features.

it would be better to say they aren’t relying on libraries and features from rivals. not that they will use “no code” from them, good code is good code afterall

Boring hit piece that way overblows some issues on the topic.

Yeah, can’t say I really care about this, this seems like a bit of a nothing burger.

maybe if any of those open source github alternatives were actually any decent, most of the “github alternatives” I find don’t even have a functioning search…

EDIT: I also find that github’s discoverability (like this https://github.com/topics/activitypub?l=rust&o=desc&s=updated) is actually great I find so many cool projects using it

Can a webpage glow any harder?

There are good reasons not to federate, Legality is kinda murkey when it comes to stuff like this. Federation could (not saying it would) be used as a weapon against them. I mean, there are all sorts of instances on the federated networks, many of which do not comply with US law. Not just the real shitty stuff, But even instances that just don’t care about DMCA for instance. It could simply be that Federation is just way too much of a hassle, which I really couldn’t blame them. I did try to host my own federated service instance and it was just kinda too much.

Working with android can be a bit of a pain for sure. I’m only talking about android here since that’s all I’ve tested, so don’t apply what I am saying to chromium, Android and Chromium are two seperate projects, by two separate teams. but in the end it’s important to realize that google has actually needs for these devices. As long as you work within the bounds of needs it’s actually not that hard to actually work with. Android has a LOT of stuff for sure.

Android actually allows you to configure most things (granted the documentation is absolutely horrid, Grep my beloved). It is true that most android phones are running proprietary stuff, but this isn’t really any fault of google. Google has gone to fairly great lengths to make AOSP a fairly open ecosystem. Nearly every rom is heavily customized as per customers requirements. AOSP can actually run on most hardware fairly easily. Hell it even works just fine on the vanilla kernel (Waydroid for instance). The Issue is that it’s nearly impossible to market consumer devices with only FOSS/AOSP stuff, the margins on phones are actually terrible. The biggest issue is finding a phone that can accommodate the more open stuff, not the issue with google pushing crap. In the end Google is making devices for people who will fight tooth and nail to grab the gun to shoot themselves in the foot. A lot of their motivations are based on that. But doing your own AOSP is still easy enough. Just need hardware for it.

Chromium and AOSP are not good examples for what you’re saying. Both Chromium and Android have thriving ecosystems of forks and alternatives based on them. Built on the work that Google is doing with them. So I really don’t think those are good examples of applications that aren’t healthy because you can just use a fork.

Yes, Google controls upstream, but there’s no reason why you can’t use downstream.As you said, it puts maintenance burden on the forks, but people are willing to do that. That’s the thing.

EDIT: This is my off account, So, unfortunately, you’ll have to take my word for it, but I did used to be part of an Android ROM team in the past and still do Android work private sector today.

I find that fair, but at the same time, proton has a rocksolid history at this point. OFC they will likely add their features to it, and maybe remove some. But im the end its still open source and under gpl licence, so its not like proton cam change that unless they remove all other commits.

awful name

I think you mean a great name

Yes. I have had many bugs with it, I recently changed to organic maps and have no complaints

Literally never heard of it let alone know anyone who cares…