Problem is that it not really is “just a store”. By using the google store you get access to the google play APIs, which are upgraded separately from the device OS - which is sensible from a security perspective, but they also were created by google specifically for regaining control over what goes on on Android devices.
A lot of applications are needlessly tied to play APIs - either because that way is a bit easier, or just because google is good at marketing them, and the developer didn’t think twice about it. Some relatively basic APIs are part of google play - for example maps, which needlessly is tied to google maps. Unlike Android itself the play APIs are not opensource.
Yandex tried about a decade ago to re-implement the play APIs to keep such applications working without the play store, by utilizing other services providing the same functionality, and tried to get other companies to join them. I’ve visited the Yandex office in Saint Petersburg a few times to discuss that back then (just checked, most of that seems to have been 2014 - that year Yandex was sponsoring my Russian visa). The effort failed for various reasons, unfortunately - the big one being that doing this required reverse engineering API changes on every play update google was pushing to stay compatible. There’s the microG project around now, but it seems to be less ambitious than what Yandex was trying to do back then.
My point is, as long as at least the API for play services isn’t maintained in a way that allows full open source reimplementations - or better, google releases parts as open source where we can plug different backends in - “use a different store” is not really a possible solution for many.
You’re describing Wayland running into issues due to overall high system load, and not been given enough scheduler time to accept messages?
edit: This issue? gitlab.freedesktop.org/wayland/wayland/-/…/159 - didn’t find anything else matching the description, and personally have never seen that, both on my low specs notebook or my workstation, which probably counts as higher spec.
That sounds more like a compositor problem - typically a client should not have control over where windows are placed, and that X11 allowed that got heavily abused with negative impact on UI. Wayland fortunately fixed that, so it is now up to the compositor where to place windows. Those can send hints, but the compositor is free to ignore them.
In your situation your compositor should remember where to stick the windows.
There’s a lot of other stuff where Wayland improves the experience. Pretty much everything hotplug works to some extend on X, but it’s all stuff that got bolted on later. Hotplugging an input device with a custom keymap? You probably can get it working somewhat reliably by having udev triggers call your xmodmap scripts - or just use a Wayland compositor handling that.
Similar with xrandr - works a lot of the time nowadays, but still a compositor just dealing with that provides a nicer experience.
Plus it stops clients from doing stupid things - changing resolutions, moving windows around or messing up what is focused is also a thing of the past.
You have a list of systems you’ve connected to in known_hosts, though. And the config file is easy enough to parse - throwing away the stuff you don’t care about - to expand on that list.
I made a quick plugin to also run stuff from path, and am currently working on a proper ssh plugin for that - extending them is a bit more involved than the simple rofi/wofi scripts, but there’s a lot more things an anyrun plugin can do.
Yeah, things are getting to the point where just having a mobile device running Linux and using Waydroid for some useful Android applications is less painful than trying to make Android work.
I’ve been using (or, in some cases, trying to use) that when it was brand new. Kernel side was relatively easy - but there was a lot of compiling custom versions of XFree86 trying to get acceleration working properly.
On the one hand a bit sad to see that kind of history I’ve experienced myself go - on the other hand, it’s probably been a decade since I’ve last used something without KMS, and the ease of use of modern KMS drivers is way ahead of all the older stuff.
In IT contracting (at least the fields I’m around) it’s quite common that “being able to acquire new skills quickly” is one of the skills you get paid for, and the time needed for you to do that is accounted for in the project planning.
A few years before Ubuntu quite a few companies tried doing their own distributions. Back then it still was common to sell them in a proper software box - CDs or DVDs, manuals and some swag, at minimum stickers, but quite often also pins or some other stuff.
On exhibitions they’d often give away full boxes to get people to try - sometimes the current version, sometimes the last release. I still have a bunch of those in the garage - I think Corel (yes, the painting program guys) should be one of them.
There’s a lot of enterprise stuff that only ships as binaries. I had some fun in the late 00s trying to find the most recent distribution still shipping packages for egcs as that was the only compiler supported by the Lotus Domino SDK.
(For the younger ones here: There was some disagreement about gcc development, which resulted in the egcs fork. It got merged back into mainline gcc by he late 90s already, though)
At the time when the Loki ports happened it was a great thing - before that you pretty much had doom and quake available. Nowadays things are better with steam, but it’s quite likely that we’ll see some stuff break there in a few years as well, at least for older games.
It’s a similar thing with four leaf clovers - I never in my life found one, even during periods where I’ve been scanning every bit of green while hiking. But then we had a friend who isn’t really paying attention to her surroundings, and just randomly goes ‘oh, moment’, and picks up a four leave clover from a few metres away.
Seems my daughter is also developing that talent - last summer she picked up a few while playing outside.
Gentoo is useless for learning how things work. Back in the 00s when I still had time to hang out at events it was always quite ridiculous at what kind of basic stuff the gentoo crowd got stuck at - and with the tooling 15+ years more polished now I’d expect what is actually going on is way more hidden than back then.
If you do want to understand how things work just build a minimal system - either on spare hardware, or qemu/kvm. Don’t go with systemd, or other fat userland options - that just makes you compile a lot of dependencies not adding value for learning.
Use some lean init (or just write one yourself), and some lean shell.