LeFantome

Everything runs under Wayland. That should be your default expectation.

At this point, Wayland is the preferred environment for GTK and Qt apps. Unless the app is exploiting some specific aspect of X11, all GTK (3 and up) and Qt (5 and up) apps work fine under Wayland.

As for other toolkits, FLTK, Electron, and SDL apps run in Wayland too.

And by “preferred”, I mean that these apps (like Thunar) will run natively on Wayland even if Xwayland is available.

There are Wayland only toolkits now but not really any “modern” toolkits that do not support Wayland. When Thunar gets ported to GTK5, it will be Wayland only.

Obviously ancient x11 specific stuff like XCB or Athena, and things built on them like Motif will require Xwayland or Xsatellite. So if you want to run, xv or motif nedit, you need those. This list includes GTK2 as well. But even they work well enough you may not notice. I mean, xeyes won’t track your mouse I guess.

And just in case mentioning xeyes brings out the Wayland critics, you can build an xeyes app that works in Wayland. I think the Wayland Maker compositor project has one for example (WindowMaker in Wayland).

Alberta just retired all their coal burning electricity generation by moving to natural gas. LNG almost by definition reduces coal burning anywhere it gets shipped.

Europe coal consumption is going up to avoid buying Russian gas.

The profitability of gas in Canada reduces investment in oil (and vice versa). Gas sells in North America for a couple bucks and in Japan for close to $12 (as LNG).

So, naturally, all the environmentalists want to stop shipping LNG.

Apparently it is more important to feel good than to do good.

All that said, I am quite happy to cancel anything that benefits Trump and his buddies.

You probably still have an FM radio in your car. You just use it so infrequently that your forget it is there.

Actually that changed quite a long time ago. Even when FM radio was still a thing, most “receivers” stopped including radio and “tuners” became on external component that not everybody bought. I think our “stereo” in the 80’s had a stand-alone tuner even. That is for a real “stereo”. Boom boxes and the like had it all built in.

The other factor of course is that tuners went digital. Most factory car stereos continue to include digital tuners even today.

WiFi is of course radio. We just tune in and listen to it differently.

If you limited your bandwidth to 20 or 30 kHz, you could build a “radio” that you manually tune to a WiFi channel frequency and that produces audible noise. You could then build a 1980’s style modem to convert the audio back into a bitstream that you could run your network connection over.

It would be about many times slower than standard Wifi though modern compression could speed that up a bit.

Winning a mayoral race is not the same as firming a majority government.

He may be popular but it is going to be as the opposition. That is an important role though.

Sad that this does not even narrow down for me what skin colour you have. Well, I guess I can eliminate one.

The official statement from the CPC pretty much confirms the culture he is talking about. This statement absolutely drips petty, vindictive, childishness.

"Chris d'Entremont, who established himself a liar after wilfully deceiving his voters, friends and colleagues because he was upset he didn't get his coveted deputy speaker role, is now spinning more lies after crossing the floor. He will fit in perfectly in the Liberal caucus," a spokesperson for the Office of the Leader of the Official Opposition (OLO) said in a Sunday morning statement to CBC News.

The industry cannot code safely. There are many reports, studies, and corporate disclosures highlighting that memory related bugs are the primary source of critical security issues in C and C++ code. That is why even NIH companies like Google and Microsoft are adopting Rust in their core products.

That you want to publicly ignore all that evidence to paint it as an individual skill issue does not come across as competent or intelligent. Few of us are going to assume your code is free of these kinds of bugs.

The fact that your have to say it so dismissively makes me think that you know it too.

Yes. There is also a GCC front-end for Rust (does not go to C first).

The timeline is not super abrupt, especially for architectures where all he is asking is to ensure that your Rust toolchain is in order. That is especially true when you consider that Rust is already well maintained on all the Debian architectures that people actually use.

The abruptness (almost rudeness) is in the second part where he basically says that, if you cannot get Rust going in time, you should just stop releasing Debian for that architecture.

It is mostly just poorly worded though. Because none of these architectures have “official” support even now. This will not be the only way they are behind. So, there is not reason to be so dramatic.

And that would be my response to him. Another option here is that these alternative architectures just continue to ship an older version of APT for now. Emergency avoided. Few of them ship with up-to-date versions of APT even now.

Another solution is to use one of the multiple projects that is working to make Rust code build with the GCC compiler back-end. At least one of these projects has already announced that they want to work with these Debian variants to ensure that APT builds with them.

So, the 6 month timeline is a reasonable impetus to make that happen which would be quite a good thing beyond just APT.

There are many other useful tools written in Rust you are going to want to use on these architectures. It will be a fantastic outcome if this pressure from APT kickstarts that happening for some of these long abandoned architectures (by the mainstream at least).

Rust is generally not going to outperform well optimized C code.

That said, it is far easier to write performant Rust code than C code. So, what we see, is that projects that move to Rust frequently see performance gains.

That just means the initial C code was not that great (performance wise). From observation, most C projects are fairly unoptimized.