barsoap

That’s the sort of thing that should just be an extension

It most likely is on the technical level, just shipped by default and integrated into standard settings instead of the add-on ones. And it's going to be opt-in, so you won't have to go into about:config to disable it. Speaking of: You're looking for extensions.pocket.enabled, it should be false. And before you say "muh diskspace" it's probably like 5k of js and css or such.

Should all be in place. Even nvidia driver support. It's one of the rare cases where I actually support nvidia on a technical level, that is, having explicit sync is good. I can also understand that they didn't feel like implementing proper implicit sync (hence all the tearing etc) when it's a technically inferior solution.

OTOH, they shouldn't have bloody waited until now to get this through. Had they not ignored wayland for a literal decade this all could've been resolved before it became an issue for end-users.

Programs can't set position or size of windows, period, at most they can ask and then hope they don't get ignored and it's good that way. Window management is responsibility of the compositor, not of applications.

At least KDE has support for it that's about on X11 level, a proper-proper solution is still in the pipeline. And yes you're seeing right it's been there for four years.

And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).

That's precisely the point: All the devs got tired of it and started wayland instead.

X12 might happen at some point when wayland is mature, as in a "let's create and bless a network-transparent protocol so we might have a chance of getting rid of XWayland in 50 years" kind of move.

Yep that'd be Wayland devs maintaining XWayland, which is part of the x.org codebase. There are no "X11 devs", they're the ones who started Wayland to get rid of that bowl of spaghetti!

I argue that X11 would have hyperactive development, if we did not have Wayland

Wayland was started by the X developers because they were sick and tired of hysterical raisins. Noone else volunteered to take over X, either, wayland devs are thus still stuck with maintaining XWayland themselves. I'm sure that at least a portion of the people shouting "but X just needs some work" at least had a look at the codebase, but then noped out of it -- and subsequently stopped whining about the switch to Wayland.

What's been a bit disappointing is DEs getting on the wayland train so late. A lot of the kinks could have been worked out way earlier if they had given their 2ct of feedback right from the start, instead of waiting 10 years to even start thinking about migrating.

Making screenshots does, too, which is why that functionality gets implemented at the compositor level. And so will screenreaders. In fact looking at my settings panel KDE does have support for Orca. Dunno how well it's working but it's not like the issue is being ignored.

That does not seem to be a stray and yes there's definitely reasons to take potshots at Gnome. They still don't support server-side decorations. Everyone is absolutely fine with them not wanting to use them in their own apps, have them draw window decorations themselves, and every other DE lets gnome apps do exactly that, but Gnome is steadfastly and pointlessly refusing to draw decorations for apps which don't want to draw their own decorations. It'd be like a hundred straight-forward lines of code for them.

And that's just the tip of the iceberg when it comes to breakage you have to expect when running Gnome.

Wayland kinda is an x.org project in the first place. AFAIK it's officially organised under freedesktop but the core devs are x.org people.

x.org as in the organisation and/or domain might not be needed any more, but the codebase is still maintained by exactly those Wayland devs for the sake of XWayland. Support for X11 clients isn't going to go away any time soon. XWayland is also capable of running in rootfull mode and use X window managers, if there's enough interest to continue the X.org distribution I would expect them to completely rip out the driver stack at some point and switch it over to an off the shelf minimum wayland compositor + XWayland. There's people who are willing to maintain XWayland for compatibility's sake, but all that old driver cruft, no way.

They have to be hotter than the temperature of the Sun

Well they don't strictly speaking have to but to get fusion you need a combination of pressure and temperature and increasing temperature is way easier than increasing pressure if you don't happen to have the gravity of the sun to help you out. Compressing things with magnetic fields isn't exactly easy.

Efficiency in a fusion reactor would be how much of the fusion energy is captured, then how much of it you need to keep the fusion going, everything from plasma heating to cooling down the coils. Fuel costs are very small in comparison to everything else so being a bit wasteful isn't actually that bad if it doesn't make the reactor otherwise more expensive.

What's much more important is to be economical: All the currently-existing reactors are research reactors, they don't care about operating costs, what the Max Planck people are currently figuring out is exactly that kind of stuff, "do we use a cheap material for the diverters and exchange them regularly, or do we use something fancy and service the reactor less often": That's an economical question, one that makes the reactor cheaper to operate so the overall price per kWh is lower. They're planning on having the first commercial prototype up and running in the early 2030s. If they can achieve per kWh fuel and operating costs lower than gas they've won, even though levelised costs (that is, including construction of the plant amortised over time) will definitely still need lowering. Can't exactly buy superconducting coils off the shelf right now, least of all in those odd shapes that stellerators use.

The ISA does include sse2 though which is 128 bit, already more than the pointer width. They also doubled the number of xmm registers compared to 32-bit sse2.

Back in the days using those instructions often gained you nothing as the CPUs didn't come with enough APUs to actually do operations on the whole vector in parallel.

Also someone who fringes the ring quite unlike any other.