I am not the biggest Richard Stallman fan, and this was also my first thought. But in the interest of truth, it is very unfair to portray him this way.
What Stallman argued for was correctness. He is guilty of pedantry, not pedophilia. Did he do it badly. Yes. Was it a socially risky position to take? For sure. Is he a child predator? Not based on any evidence I have seen.
There are actual child predators out there. Let’s focus on them.
X11 desktops work fine and will continue to work fine. But very few people will be using them in 5 years.
Why don’t you just stick to X if you think it is better?
Of course, the rest of us have moved on to Wayland because we disagree with you.
No need to fight though. Have fun.
It is a different ecosystem. It requires time to mature and yes, you have to migrate to it in order to use it.
Moving to Wayland was a bit like moving to a different operating system from an application point of view. The toolkits made that reasonably easy for most apps but they really do not help much if you are the window manager.
So yes, compositors had to be built. This was easy enough for the big projects like GNOME and KDE but a bigger ask for smaller players. But there are lots now: GNOME, Plasma, Hyprland, MangoWC, Niri, COSMIC, Budgie, LxQT, LabWC, Wayfire, Sway, DWL, River, Wayland Maker, etc. I am sure there are many more I don’t know or forgot. There will be lots more.
And yes, a Wayland compositor is a bit like the X server and window manager combined. So, they are harder to build. Except libraries have appeared to do that. There are wlroots, Smithay, aquamarine, Louvre, and SWC. There will be more. So, a Wayland compositor is not really that much harder anymore. And it will get easier.
The XFCE project is just starting a Wayland compositor project now. It will be built mostly by a single developer. They think they will have a dev release in a few months. They are using Smithay.
Building the Wayland ecosystem took time. But we are basically there. And it is only going to get bigger and better.
CodeWeavers, also a for profit company, has indeed been at it for decades. I used to pay them to run Outlook something like 20 years ago.
If you want to imply that Valve is not contributing, your own statement works against you. Wine is not new. CodeWeavers is not new. Yet gaming on Linux only really became a thing once Valve got involved.
Most people still cannot install or configure Wine. But they can use Proton in Steam. People gaming everyday still cannot get Office or Photoshop to work. They can play Steam games but would struggle to make StarCraft run (not in Steam).
Valve is organizing all the bits to make an actual ecosystem work. It is why they created Proton vs just sending patches to Wine. It is why they have gamescope. It is why they fund FEX. If is why they created the Steamdeck and Steam Machine.
I have loved CodeWeavers literally for decades. But minimizing the impact that Valve has had on Linux gaming makes no sense.
This has been so much of the problem. The only light at the end of the tunnel is that it is literally just a matter of time until these users catch up and stop complaining.
I was excited thinking this was 3.2 and then let down to see that it is just another 3.0 update.
3.2 may not “punch Adobe in the face” but it is going to be a solid release. Most importantly, it will show that GIMP releases do not have to take years. If the time between releases drops, I am hoping that will attract more developer interest.
A better “punch Adobe in the face” candidate may be the 3.4 release. It is possible that it will finally include full support for CMYK.
Anyway, good to see a GIMP release of any kind, even if it is not 3.2 just yet.
If you like Paint.net, try Pinta.
Sure.
But “missing significant foundational and complex functionality is not really a bug”, it is a feature. I mean, I guess I could file a bug that says “won’t run ALL Windows software” and talk about how long it stays open.
As each of these dominos falls, it gets easier to add more functionality on top. I feel like they have made more progress in the past two years than they have in the 10 before that.
Given how slowly they move, the obvious choice is to bet against them.
That said…
It already works for some stuff. There are already people that have been able to use ReactOS to run legacy but vital applications. I cannot remember any details but I have heard of a few instances where businesses saved rather substantial amounts of money with ReactOS.
Similarly, there are certainly people that find it runs the particular applications they want and runs on the hardware they have. Some legacy gamers use it. But perhaps you have hardware that is only supported under Windows XP.
And, if people keep using Windows, it will eventually become usable enough to be a viable alternative. If it had Windows 7 level features today and ran modern apps, a lot of people would find it good enough to switch. It does not have to be better than Windows or support every Windows feature.
As slow as they are, they have gotten further than most people would have expected.
So when I install EOS for the first time, I should use the ISO from when the project was founded?
This comment is silly. The fact that every rolling release I can think of tracks against releases in exactly this way is not.
Of course they do. It is a silly comment.
Now that GIMP has finally released version 3, they seem to be moving faster. I hope they are able to get more positive mind-share.
For example, they are close to releasing 3.2 that already has lots of great stuff in it. It looks like 3.4 could address some really long running deficiencies like native CMYK.
If stuff actually gets released, they may not only attract users but developers which is what they really need.
Lots of nice changes in this release. I see lots of the things people complain about.
I am not a GNOME user myself but since Niri uses XDG-desktop-portal-GNOME, this looks like a release to look forward to.
I have mixed feelings about Zorin.
They are doing a great job of promoting themselves and in attracting converts from Windows. It seems like a nice enough distro as well that users are likely to have a decent experience with.
On the other hand, they are charging money for a “pro” version that mostly just bundles software that users could get for free. My first reaction to this is that it is exploitive, both of uses and software devs.
But then I remember that they also offer support and I think that introducing people to software they did not know about is also a service.
And if they use the money to do all of the above, the Linux ecosystem benefits. So, perhaps they are not that bad.
Perhaps the best thing about them is they make it harder for truly scammy “windows” distros like Wububtu to take hold.
If they start to make “real” money, I do hope they share some of it back with the projects they leverage.
That is pretty limiting solution though.
First, you can only have one libadwaita library installed. So, if GNOME is already on a system, installing another DE alongside it will create a conflict.
Second, livadwaita is not designed to enable third-party theming. It surfaces the capabilities desired by GNOME, which is less and less all the time. That limits what others can do.
Do you mean by supplying your own version of libadwaita?
Absolutely GNOME.
GIMP just finally finished their port from GTK2 to GTK3 a few months ago. GTK4, released 5 years ago, has literally nothing to do with them.
Like GNOME, I think that GTK is one of those projects that now says that the letters do not stand for anything.
It has really only been a problem since GTK4. A lot of the rest of the GTK universe has stuck with GTK3. Now we are seeing people come up with alternative versions of libadwaita.
We should end up seeing a fork on the GTK side with GNOME going one way and everybody else another.
What did you replace Xorg with 10 years ago?