drwankingstein

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).

I have a 12vdc direct power USBC charger for my tablet. This will totally fry any normal USBC device it touches.

can't say I have experienced that. I use a myriad of modern but lower end systems and stuff like dinit still uses less resources and is in turn better for the speed and responsiveness of my systems

this is pretty much how it works in some cases, you need to port from one protocol to another, or to a different system altogether.

I'm pretty sure everyone has settled by now, Personally I hate systemd. It's slow, relatively resource intensive, poorly designed in many aspects.

but as an init and service manager it's the best. Though I do have to say dinit does get pretty close for me now.

I personally use Arch on my desktop and artix on my laptop. I want Systemd to die just as much as the next Systemd hater, but unfortunately I don't believe we have anything better yet.

that's just the thing, This is again, more fragmentation, Some compositors support always on top, some don't, you choose x protocol for your app, and now your app works great on sway, but not on KDE or gnome, or it works great on gnome and not kde or sway etc. As an app developer the situation is a bloody joke. My current stance is "just use xwayland because wayland will never be suitable" and thankfully with cosmic and kde both supporting "don't scale xwayland" this seems to work well.

EDIT: they also make enough deviances from the upstream protocols that this can't really be considered a "experimental branch"

EX: https://github.com/misyltoad/frog-protocols/blob/main/frog-protocols/frog-color-management-v1.xml vs https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14/diffs

Yay, another set of protocols that will just lead to more and more fragmentation.

You do acknowledge one issue with Wayland, probably the biggest issue with Wayland, but then fail to acknowledge the second biggest issue with Wayland being fragmentation.

Solve one issue by making another issue worse.

Nine times out of ten, running chown on Android is an astronomically bad idea. 10 times of 10, what you're trying to do right now, is an astronomically bad idea.

What is it you are trying to do? Or rather, why?