says "true variable refresh rate" support, is not true variable refresh rate support...
Well thats click bait and a half
None of them are really great, Im hoping cosmic in the future will be, as it stands.
"Touch primary" DEs (IE. Phone, tablet with no keyboard or detachable etc.) I think are the way to go.
Plasma mobile is king 100% nothing gets remotely close right now.
Phosh I found far too buggy, and the apps are far too limiting. Things like squeekboard for instance don't scale properly, I had issues running chromium browsers on it too.
Ubuntu touch uses lomiri which im sure is great, I havent had luck running lomiri on any "common generic PC" linux distros. I did try getting it running on arch but found too many issues.
swmo is nice in theory, but it's missing a lot of the ergonomics.
Plasma mobile is missing a lot. It has some not great design choices I find, however it by far has the best app ecosystem in terms of actual app quality, as well as actually working fine on tablets and phones alike.
For touch secondary experiences I find KDE and Gnome to be just about as you would expect, Both are fine and mostly navigatable on touch only stuff, I would say KDE is often a lot better in terms of responsiveness, Gnome I can find bugs out as @that_leaflet@lemmy.world said. That being said, In portait mode, KDE is down right terrible some times as many KDE desktop apps have zero support for portrait aspect ratios, and you are relying on scaling being "low" enough that the app can fit fine anyways.
as for some stuff you can look forwards to in the future, We are starting to see stuff like catacomb which is designed for phones. I also had some actually great luck with Niri but it's mostly just buggy, and you still need something to manually launch keyboards.
In terms of applications, I have absurdly high hopes for cosmic apps. Each one I have used this far has a "tiling first" design policy, which translates pretty much 1:1 with being flexible for a phone it turns out, While cosmic apps have really poor touch support, if you install them and pretend your mouse is a finger, you will find that each one is almost perfect in a phone form factor.
EDIT: I wish I could say linux touch was in a good spot but realistically it's not. I personally recommend just installing something like Bliss or using waydroid as the primary experience. I am very active in the bliss community because in large part tablets and touch support. Android is still far better then linux is in general, even if a little less flexible, you can have a fully foss install like what I have personally.
Was this the git hosting service that wanted to have things like federated (in this case im talking about cross instance) cloning, searching and issue hosting?
I may be mistaken in general but iirc there was a hosting service like this that I found super interesting, especially in light of things like DMCA abuse against projects hosted on github and gitlab.
EDIT: seems like it is one of two, forgefed is a protocol it will use, activitypub one, very interesting.
My name is Linus torvalds and this is why I TempleOS...
This would be a great comment if this was America...
Why? Hyprland has been limited by wlroots multiple times in the past.
Do we really need to be so constantly cringy about it? Yes, custom ROMs are great. I run one. Lots of other people run one. They're great. Don't get me wrong. But you have to realize most people simply don't care for one, Most vendors also don't really support their phones well under GSI, so things like camera and stuff like that hardly ever work properly.
In a lot of cases, it is quite a bit of work to get a custom rom flashed and have it working well. The technological skill gap between most people who will run an Android phone and even enthusiasts who will so much as think about installing a custom ROM is so massive that you may as well be a hacker to them.
we already have them. It's not hard to make a firearm, and the 3d printed weapons scene has taken off quite well. all of the good ones still need metal parts ofc, but they are pretty easy to get your hands on in many cases.
not enough guns, needs a rifle and a shotgun at least.
Not sure how long this will last, but here are some videos I took of it, try not to mind the crunch on the last one, I had to use qsv_vp9 for it since I was running out of time and space. Also don't mind the fist video's bad fps, I was compiling in the background and forgot.
Simultaneously installing apps: https://cdn.discordapp.com/attachments/719811866959806514/1217198163149197332/record.mp4?ex=66032720&is=65f0b220&hm=b1e495b579a5313cbaf0f3046ba78479f51dd44fa9f8ecf21929784c27fcbd66&
Plasma mobile on x86 tablet vs gnome software: https://cdn.discordapp.com/attachments/719811866959806514/1217287580916125818/tablet.webm?ex=66037a67&is=65f10567&hm=c4afb4d964b35e04f0a4b12d387a5110403ecf74d267747b5dc2738ff12166bd&
This is understandable, and honestly xwayland is great, even with fractional scaling now, at the very least on KDE. I think simply relying on xwayland is a very viable solution now for a lot of apps. and it helps work around a lot of issues so that's always a major plus
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.