Quackdoc

wow I'm sorry, must have been really tired, I mean appimage, it being flatpak only is the issue.

Good touch support. Using termux has more then sold me on it, While many terms to support touch, I do often come across some that don't. Otherwise i'm a simple man, be fast enough, work with one of the "major" image specs like sixel or whatever and do the basics and im set.

cpak is still containerized, I would like to install natively, or via flatpak

I really just hope they reverse decision on making bottles "containerized" only.

Yes it is, but it's a necessary one. People aren't going to go out and learn new tax software. and hell, I still have yet to find a single working crochet program on linux.

Thankfully compatibility now isn't that bad. I actually did an experiement where I ran entirely in wine's desktop for a week and it was surprisingly usable.

this is not true. SO many people will download and install whatever. I still get my old customers calling me up for help because they installed some registry cleaners promising to increase their performance by 5x

As someone who used to sell computers to elderly and people who are generally non tech literate, as well as ran computer literacy courses;

ChromeOS + something like flatpak. I don't think anything else will really work in the current linux world. Holding on hope for Cosmic based DE.

A Distro must have

• Easy AND reliable DE. KDE has been way too buggy and gnome has been way too hard for my parents to use. Old people often have an extremely hard time learning, it needs to replicate what they already know which is either going to be Windows or OSX most likely. Cosmic should be able to do both nicely when ready.

Reliability is so fucking key here I can not understate it. The computer glitching out is entirely unacceptable. They will not be able to do any debugging nor will you likely be on call 24/7 to fix their issues. They also need security so you can't just "set and forget" either with no updates in a false sense of stability. Older folk copy and paste shit. Permissions and stability is key here. Flatpak has a lot of potential but it's not there yet.

No real time AV really hurts here.

• Extremely strong app selection with either android or wine app support. Wine is the most preferable. A lot of people are reliant on windows programs for things like tax filing and all sorts of stuff like crochet software and what not. Android apps however can often be good enough and are extremely simple so with a little help, and you will need to help, they can get by with android app support.

• A11y, screenreaders, OSKs, maginifers etc. We need all of it if we want to fit the "generic elderly support"

• Good performance. Elderly people do NOT like updating systems, Their systems will likely be old. And well they are old too. If a system is slower then what they are used to, and generally non responsive, they may think the bloody thing is broken. ~~cough cough gnome cough cough~~

I genuinely do not that that any DE let alone distro is an acceptable daily driver for "general people" because general people have such a wide variety of use cases and needs. Some folk need crochet and tax software, some folk need CNC software like stitchfiddle, Some need magnifier glasses and speech to text. and man, this is only the more common of things i've seen.

Remeber folk, a PC that does 99% of what people generally need, does not mean that it will fit the needs of 99% of people. Here is hoping to a bright future, but I don't think it will be a close one.

This is not traditional VRR how we think of it. VRR how we think of it is changing the "frame rate" of the monitor to better suit the frame pacing of the received frames, this is not whats happening here. This is how things like freesync works. It takes your device framerate, say 60fps, and slows it down to better match the frame pacing of the content, say 48fps. Now the monitor doesn't physically change states or anything, it just allows flexible updating to match the frame pacing.

You don;t get this with this adaptive refresh rate method

Here you are effectively getting a noop every refresh cycle it doesn't need. It's still good, but not as good as what most people think of as VRR (Freesync/vesa adaptivesync, gsync etc.). You are limited to the steps your display can output. For this to be useful you require a high refreshrate display like 120hz because each application needs to align with a frame refresh.

IE. say you have a 24fps video, the display won't change it's frame pacing, but rather you get a noop every 4 frames and a refresh, (24 * 5). Now assume you have a 90hz display, 24fps has no solid divisor in 90fps, so you have to either wait for sync, or get tearing. The first one leads to judder (which can probably be mitigated using offset sync waits?) the second one is well, tearing.

says "true variable refresh rate" support, is not true variable refresh rate support...

Well thats click bait and a half

I'll try it out for sure. Last time what tried river it was fairly basic. So if it's come a long way that's quite exciting.

Click baity title aside. This is actually pretty much pretty true. What the vast majority of people want when they're writing their own composers seems to be specifically the custom window management aspects.

And it is true that even with something like Wlroots or a Smithay, it is a lot of works right your own composer and have it be "competitive". And he is right. There are a lot of composers out there that are just not usable for anything more than the basics. And there are tons more which are just toys that have been abandoned that aren't really usable. That being said we saw a lot of that with window managers, But yes, writing a compositor is a lot more then writing a window manager.

I personally don't use hyperland, but I can see the point he's trying to make, and I think it's a rather good point. I think if we had more compositors that focused on having a scriptable window management, then that would be for the better.

I don't really see this as toxic either. I mean, if it's toxic to call a composite or trash in one way or another, then I would argue that 90% of the Linux community is far more toxic than he is. It's just a matter of truth. Wayland is a big complicated thing with a lot of protocols and some of it is poorly documented.

And of course, this is him shilling his own composter. It's his own composter, and this is the blog about him making his own composter. Of course he's gonna put a post on it, shilling his own compositor.

That being said, As I said earlier, I would like to see a more scriptable take for things like window management. I don't think hyprland has to be unique in this aspect, but as it stands, it most definitely is.

pardon my weird language, its hard to use STT.

this is a massive issue even on my tablet too, but many toolkits have this issue