Andreas did not like the Rust community. It sounds like that is still true.

He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.

It is telling that the first project was a total rewrite of the entire JavaScript engine. There is no shared hierarchy and a well defined boundary between the C++ and Rust code. That may be a sign of things to come.

We may see entire modules that are either all Rust or all C++ rather than more fine grained mixing.

It IS the early days of GNOME. MATE started with the source code of the last GNOME 2 release.

MATE exists because people loved GNOME 2 and hated GNOME 3.

And totally ineffective if the other two parties are already colluding (which we are).

It would hurt but honestly I would be ok if Canada stopped trading with the US completely.

First off, do you have evidence that negotiating with terrorists is a historically successful strategy? Because otherwise, I am not sure why you are suggesting that Canadian capitulation has any influence over US tariff policy.

Second, who has had famously higher egg and dairy prices over the past year? The US or Canada? If the goal is lower prices, which administration should we be cheerleading?

I will am pretty free enterprise but I will take “price fixing” over submission to an abusive and unreliable narcissist every day of the week.

The idea that the biggest threat to Canada right now is internal economic policy is laughably disconnected from reality.

How about some of us choose with our heads. That sounds like an idea.

Maybe not “dead” but it is permanently broken.

Also, get the numbers right. Two thirds of Americans did nothing to keep Trump out of office.

The midterms have not happened yet. We will see.

What riding is this guy in? I think we should show him what a real hissy-fit looks like.

You do not need to understand anything about X11 vs Wayland. Use whatever your distro of choice defaults to.

Wayland is the future. Every Linux desktop user not fighting hard to avoid it will be using Wayland in 2 years. The majority are already.

Wayland and X11 are both protocols. They are a way for graphical applications to talk to a “display server” (your graphical desktop).

X11 was invented in the 80’s. Until recently, there was essentially only one surviving implementation on Linux—something called Xorg. While Xorg was the display server, you had to add something called a “window manager” to control what your desktop would look like and how windows would behave.

While Wayland essentially does the same thing as X11, it was built to quite a different set of design criteria. If you have not been part of the history, it is not worth knowing about. Security is one of the big improvements.

Perhaps the only detail worth mentioning is that the display server and window manager functions have been combined in Wayland into something called a “compositor”. So while everybody was using Xorg back in the X11 days, there are many competing compositor implementations in Wayland. They differ not just in how they manage windows but also in how them implement many other details like how to take screenshots, manage multiple monitors, or handle scaling. There are a set of standards that define this behaviour. It is a bit like the web where you have different web browsers and web servers but the same web applications work on all of turn (which perhaps some small differences).

The two systems both “do the same thing” and are quite different at the same time. If you use one, switching to the other may seem painful as things that worked may not anymore and even things that still work may be done differently or require quite different knowledge. Not many people switch from Wayland to X11 but anybody that used Linux 5 years ago has had to switch from X11 to Wayland (or feel pressured to). Not all of them are happy about it. Some of them rely on workflows that Wayland does not yet or many never support. These people consider the switch to Wayland a really big deal which is why you hear about it so much.

But, if you already use Wayland, ignore it. Everybody will stop talking about it soon as almost everybody has switched. The majority that have not switched are using popular desktops like Cinnamon or XFCE that have also not switched. They have not switched as they want to make the transition very seem-less for their users. Which also means you do not have to think about it. One day they will move you and hopefully you will not notice. Or, even better, it will seem like a bunch of new features in a new release.

That amount of money is one developer full time maybe. Which can make a really, really big difference for an Open Source project actually.

I hope they do not take their foot too far off the gas before completing their Wayland transition.

Once KDE, GNOME, COSMIC, Budgie, and Cinnamon are all Wayland, 90% of all Linux desktops will be Wayland. With XFCE, it could be 95%.

I am looking forward to essentially all Linux desktop users being on Wayland so we can stop acting like it is not already the norm or even pretending that it is not going to happen. I am looking forward to putting it behind us and we are so close.

At the same time, I have a lot of respect for conservative desktops like Cinnamon and XFCE that, while acknowledging that Wayland is the future, are taking great pains to minimize disruption for their current users and even to allow users to keep X11 as a fully supported platform. I am all for that.

I do not expect Cinnamon to maintain X11 as an option very long after they switch to Wayland as the default. First while many distros ship Cinnamon, it is really a product of the Mint project and Mint is very much a Linux Desktop. Second, Mint does not have the resources as they point out in this article. Of course, I could be wrong.

XFCE will probably keep X11 around much longer. First, XFCE is very popular in non-Linux settings. But mostly I say this because xfwm4 itself takes very little dev effort and it is the only XFCE component really tied to x11. Xorg is essentially in features freeze. As long as XLibre does not break everything, xfwm4 will just continue to work. The other components of XFCE work fine in both environments already. The goal of xfwl4 (the XFCE Wayland compositor) is to mirror the xfwm4 experience. And xfwl4 is deferring to other components to define behaviour (eg. xfsession and xfdesktop). So, it should be easy to keep the overall XFCE experience in sync on both display servers without much wasted effort.

I have well over a dozen Linux machines running in my home. More than half of them would be considered garbage by most people. Clearly, I disagree.