Quack Doc

I have been looking a LONG time for a consistently stable distro, ill let you know when I find one in approx 20 years

this doesn’t apply here. hyprland has announced that “all your wlroots programs will still work”. so they are keeping support for wlr protcols

is another big factor, and probably the one that finally tipped the scales

means that it is not the sole motivating factor.

which means even if they are literally adolf hitler, I shouldn’t care, as long as they don’t post about gassing people on my server

Literally means that if they go around spewing crap, they get dealt with. This is not condoning hateful trolling at all. He is on the free speech side of things, but that doesn’t mean he condones it at all. If you start posting bad crap, you get dealt with. Minor slights, are as the name implies, minor. Those are allowed but within strict limitations, if you start going full blown idiot, you get dealt with.

the blog post inside the linked blog post goes over some points. each point is copy and pasted more or less.

• like for example the multiple times I’ve spent dozens of hours debugging a single issue only for it to turn out a small typo or a careless mistake that any language would catch at compile time, except for C
• Memory safety issues arising from the absolute lack of any documentation whatsoever of wlroots have also been quite the annoyance
• The development of a display server is very complicated, as they are very broad and complex pieces of software. Mixing a C library with 0 documentation is basically asking for trouble.
• new wayland features that require changes in wlroots tend to take ages to get merged into wlroots, like for example tearing, where a basically ready MR took 9 months to merge
• explicit sync still not being a thing, despite KDE and Gnome having implementations already (I believe it is now, but not at the time of the blog post)

Wlroots has a slow development time for features hyprland wants, as well as hyprland having a different release cycle then sway, often causing packaging nightmares.

violated their code of conduct in places where the code of conduct explicitly does not apply is extremely important here. He never once violated code of conduct anywhere that it did apply, and in public spaces was quite respectful, You could for sure find faults with him, but you could find way more faults with most other developers who still actively contribute to projects hosted on FDO.

Exactly, vaxry apologized for the lack of moderation and took changes that prevented the incident. to which FDO said, “he we are onto something, we can push our divisive politics here” then got angry when he rightfully told them to fuck off

Partially, it also had strong technical motivations.

Wrong. This was originally technically motivated as hyprland had been limited by wlroots in the past and often had different update cycles from sway causing packaging issues.

Vaxry never condoned hateful trolling of trans people. In fact, he publicly acknowledged, and apologized for the lack of moderation that lead to the incident, said he would do better, DID better, and THEN after everything had blown over FDO tried to ego butt into his server even more.

Why? Hyprland has been limited by wlroots multiple times in the past.

This is for sure the case for vendor solutions, but AOSP itself is still quite the lean OS. Android also has GO variants which perform even better at low resources, (Bliss also has builds of these if one is curious). They are extremely responsive. I don’t think Bliss as A14 go builds, but we do have A13 go builds, and they are extremely responsive on very low end hardware, the bar is actually support for SSE.

Bliss currently has a hard requirement on SSE 4.2 or greater due to a load of changes (occasionally some work is made on lowering this but it’s slow and a lack of real motivation), but pretty much everything I have tested that is supported works fairly well, from my old i3 desktops, my atoms and celerons etc.

it should have pretty good support but you may need to use this script to spoof the device for some stuff https://github.com/Quackdoc/waydroid-scripts/blob/main/spoof-device.sh

its easy to test BlissOS is open source and can be installed on any relatively modern PC or in a VM, coms with foss and gapps variants, install foss

this really isn’t true at all. android works great on 2Gb of ram, you don’t really hit issues until you load gapps. If you don’t it works great. I actually run BlissOS on my old Asus t100ta and Im not the only one.

When you do nothing something like xfce works great, but when you actually start doing things like browsing the web, watching youtube etc then it starts to really become a slog. Meanwhile something like BlissOS is actually usable even when watching 1440p content (gpu not strong enough to test UHD)

ah my bad, I misread, I thought you had tried sudo waydroid app install.

Failed to get service waydroidplatform usually happens when something fails when communciating to the container, this usually means the container is partially loaded so you will need to stop it and start again, you may even need to do a full reboot

currently hyper-v has no graphics, qemu reccomended but hyperv should work if you force sofware rendering for gpu

google play games is still really good, it’s more or less just android inside of crosvm, usually android emulators are based on virtualbox, some are based on qemu

libhoudini is optimized for Intel, NDK for AMD, but some apps may be incompatible with one or the other.

The charm of Unix systems used to be flexibility, buy Wayland seems to be an extinction-level event for traditional window management. Nothing fills the gap of FVWM or WindowMaker. But gosh, I can get 92 flavours of tiling compositor and windows that ripple when dragged.

I think this is “temporarily” true as we get more kits that make wayland development trivial I think it wont be so bad, right now wayland is still very immature, and will be for a long time.

for many people YES! Both wayland and x11 can work very nicely when nested. For many people wayland will be remain unusable for a very long time, and for many other they are finding that now x11 is unusable for them.

It’s not a great situation, but with xwayland and running wayland compositors nested (really wish we had an “way11” too, but per app cage works for me) many people’s usecase will remain to be covered