Maybe windows rules will now work properly instead of being buggy and delete themselves…fingers crossed Imho KDE is too big, there are so many cogwheels they miss the opportunity to actually polish each and every aspect.
Up until February this year, I was still using a 14 year old DDR2 desktop. Windows 10 started to get quite slow and had some annoying crashes (mainly the fault of my goofy old hardware, of course)
I learned about Linux as an alternative through a Linux Tech Tips video about gaming on Linux, and Valve’s announcement of the Steam Deck, I was also interested in FOSS apps as alternative to proprietary ones.
Decided to try Linux Mint. With no prior experience with Linux, lack of luck finding good tutorials, and some weird thing happening with my games not launching, I had a very rough start.
But thanks to Mint, suddenly my DDR2 desktop got a lot smoother :D also, all of my drivers worked out of the box, and I got very surprised with Linux’s plug-and-play hardware capabilities.
So I decided to learn how to use it, tinkered alot with my system, and broken it alot! It was kind of frustrating, but fun at same time.
And without noticing, I had already learned lots about Linux from a more technical, and then, philosophical point of view.
Now I’m a great fan of Linux and FOSS, and have been helping friends to move to it by giving support with issues I had in the past.
I don’t get the hate for Ubuntu, it just works. For those who don’t care what setup in their system. Especially those who are coming from Windows or MacOS its a good stepping stone.
A Debian blend like SpiralLinux might be better for less technical people. Debian is one of my favorite distros but it’s pretty bare bones and requires some configuration to become an everday usage desktop.
wp-fractional-scale-v1 to allow clients to submit buffers with a non-integer scale factor matching the output.
This hopefully means Sway and similar will support real fractional scaling for applications, not just the compositor fractional scaling we already have.
But I don’t know much about application support. Qt and Electron might support it; GTK 4 does not, possibly in a future version).
tearing-control to allow clients to opt-in for tearing page-flips.
That’s great for those who need it. Anyone with a modern display should probably just use variable refresh rate (vrr), but even today some devices don’t support it. E.g. there’s been 240Hz laptops without vrr.
I was sure I read that GTK wants to support true fractional scaling in GTK 5, but I can’t find a source to it. So it was probably just speculation. As far as I understand it, it would require big changes to GTK because everything is build with integer scaling in mind.
At least GTK 4 already has support for this fractional scaling protocol.
At least it does not look blurry with fractional scaling enabled, which is the biggest issue IMO. The current hacky way is not ideal I agree but at least it is functional
I ordered one. First units should be shipped early December. Right now they seem to be some out - just few days ago you could order with 7-8 weeks delivery, now it’s just ‘notify when available’.
Distrobox is directly inspired from Toolbx and was created because of limitations of Toolbx and how Toolbx’ maintainers didn’t want to implement some features at that moment in time.
Currently, Distrobox is almost a superset of Toolbx. Though, I’ve come to the understanding that Toolbx does better at some tasks.
If you would like to stick to just one of them, then Distrobox is probably still the better one and should be preferred. However, if its added functionality doesn’t do it for you, then please feel free to continue using Toolbx.
Why is toolbox preinstalled and not distrobox?
Because Toolbx predates Distrobox and is developed by developers that are associated with Fedora and even specifically designed in hopes of solving some issues pertaining to Fedora’s Atomic distros.
i think that the libreoffice people should have re-joined openoffice once their main gripe (oracle) was out of the picture, which wasn't long after they split-off and released their first forked version.
The only benefit that OpenOffice had was the name. Given the momentum that LibreOffice had early on, OpenOffice should clearly have joined with them and maybe ceded the name.
I am glad that LibreOffice did not try to merge back with OpenOffice as clearly it remains a poorly managed project. The continued existence of OpenOffice is doing tremendous damage to the wider ecosystem. The fact that Apache continues to promote the project not only reflects badly in them but show what poor stewards they are. I would not have wanted their lead ship to have hampered the subsequent success of LibreOffice. The whole episode just proves that LibreOffice was right to break away and not just because of Oracle.
I don’t think a good response to " breaks " is to say "yes, because was designed to work with and hasn’t been updated to use ". Part of the task of replacing something old - onerous though it be - is to provide a smooth route to support old programs and functionality.
Wayland deliberately broke everything, but then was rolled out prematurely at least on some distros, before giving the vast X ecosystem enough time (which was guaranteed to be a long time, due to how large and entrenched it was) to update. Besides which, the “OUTDATED” post has an awful lot of things you acknowledge are still issues!
I would argue that promoting Wayland as production ready is still premature considering the number of excuses Wayland proponents have to make who is at fault for Wayland’s shortcomings (Nvidia seems to be a big one but people who have needs the short-sighted protocol design didn’t account for are a close second).
The problem, as I see it, is that the author of the original Gist does not really want wayland replacements for what he has, but rather what he has to also work on wayland.
Wayland didn’t break everything. It broke what relied on X11 specific stuff, which turned out to be a lot of things. The vast majority of issues still present with Wayland are edge-cases that will only see the light of day when the people with those edge-cases start using wayland. And as long as distros default to X11, that won’t happen. So that distros, like Fedora, started defaulting to Wayland “early” on (yes I put early in quotes, because it’s only perceived as early) is actually a good thing. Makes the compositor developers aware of edge-cases they can’t catch themselves.
I’vge been using Wayland exclusively for over a year and apart from a couple of small bugs, not even missing functions, I haven’t experienced any issues relating to Wayland directly. But that’s for my use case. YMMV as always.
The problem, as I see it, is that the author of the original Gist does not really want wayland replacements for what he has, but rather what he has to also work on wayland.
It's like the Windows users expecting to use all the same software on Linux when they move over problem, but in microcosm.
The main issue here is not that some of the issues that are mentioned there are not genuine. They indeed are genuine and have mostly already been notified to the devs working on the protocols and the compositors. The issue here is how those are presented. By creating this almost cultish “battle between the 2 display servers” thing is not productive and demoralizes developers. Making criticism is one thing and productive but “boycotting” is not. And certainly not in the bad faith way the author of that article has done. I myself have both X and WL setups and I alternate between them frequently. I am not sitting here “boycotting” one display server in a prejudiced manner. This is Linux, not Windows or MacOS. Users are free to continue using Xorg and develop it according to them if they do not like something else. And similarly, they are free to use Wayland.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.