sprash

It's a matter of funding. X11 development is not funded anymore whereas Wayland is heavily funded through proxies like Collabora or Igalia. It is unclear who are the originators of that money since those proxy orgs don't disclose who funds them.

Since Wayland is a horribly complicated protocol that makes doing even the simplest tasks a major chore I would consider it sabotage. There are multiple billion+ dollar corps out there with a severe interest in a non fuctional FOSS ecosystem.

Most of the time will be spend on undocumented corner cases of third party hardware and dealing with various race conditions. Even though the PCIe protocol is reasonably simple the devices attached to it are not. Since this feature is only viable if it works 100% reliable the rule of thumb is the last 20% of problems will cost you 80% of the time.

The equivalent to flushing your register state is more comparable to a context switch than a complete shut down. Also Thanks to PCIe CPU swapping could be done in pure software at the OS level. No further hardware changes required. Simply copy the contents of your RAM to the other CPU card and manage the hand-off. This is clearly different from a complete shutdown e.g. all devices on the PCIe bus would be able to keep their state.

A good programmer familiar with the target OS and inner workings of PCIe could deliver a working prototype within a week, production ready within less than a year.

If you have switched PCIe anyways I would have loved a Mac Pro with a "passive" switched PCIe backplane where you can hotplug PCIe devices in including M2 CPU PCIe cards. Also polish the OS accordingly that you can upgrade/switch your CPU in live operations without shutting down the OS or may be even run Apple silicon CPUs and x86 CPUs alongside.

"divide et impera" is not exactly a new concept. Maybe you should brush up your greek philosophy.

Obviously not. Thanks to "plurality" people are occupied with fighting each other instead for themselves against rulers that repeatedly act against their interests.

Occupying forces are in control of the state media obviously. But since their influence on people blow 70 years of age is going to zero fast more migrants are needed.

And having experienced mass migration first hand I can assure you: more immigrants means more disorder, more violence, more cost for social net, less quality of life and lower wages across the board. My experience with migrants is 100% universally bad. And I'm absolutely serious about that.

Indeed. The social cohesion in Germany was bad to begin with. This is what happens when you are occupied territory for more than 70 years. But mass immigration destroys the last glimmer of hope for self governance.

You won't and that is the point. A population without social cohesion is easily governed.

If you are looking for static system wide key remapping on the console without additional dependencies, extra software or running daemons the program "loadkeys" should be working on any Linux system. Configuration on startup is dependent on the distribution.

Yes, the result is obvious. As soon as you introduce feminism birthrates are tanking. This can be observed observed across the globe. Couple this with the establishment of contraceptives and acceptance of abortion you get a recipe for annihilation.

Not real enough. This has the original vt100 firmware ROM built in and executed by an 8080 emulator:

https://github.com/larsbrinkhoff/terminal-simulator

And Palm devices.

As far as I understand it WebGPU is just a thin translation layer to binary SPIR-V with fake Rust syntax. Is it really faster than GLSL?

The lack of important language features like function overloading or clear client side code separation via preprocessors is annoying. Also misleading notations like mat4x4<f32> instead of mat4 that imply that you could put any type between "<>" and expect it to be hardware accelerated which is not the case. Finally, the lack of assignment and ternary operators and forced bracing will make your code look really ugly.

I don't like it. It would have been better if they simply extended GLSL to cover the full SPIR-V capabilities.

The target audience for RHEL desktop/workstation use is government employees. Those people are not supposed to use the computer beyond a narrow scope of tasks. Creativity, self-responsibility, individuality and out-of-the-box thinking is discouraged. Wayland is perfectly suited for that.

Xlib is actually somewhat easier to use than xcb. Xcb however has better support for asynchronous operation. In case of xterm this wouldn't help latency much but would greatly improve throughput.

Maybe I'm doing something wrong but the RTC lags about a minute every three days. At least for my device a regular ntp sync is therefore absolutely required.

I have one of those. It takes a lot of work writing embedded C code to make it do what you want. In my case it was displaying a calendar and the moonphase. The default software is very bare bones. Battery life is 1.5 weeks for me when using ntp sync once a Day and a display update every minute without any further wireless communication.

I find the PineTime more attractive because it has an aditional heart rate sensor and a color display with similiar battery life.

Sadly bigger projects like GIMP or Inkscape didn't learn their lesson. Since version 3.0 GTK serves only GNOME and their particular demands for their severely limited desktop environment. The correct action would be to go back to GTK 2.0. It is far easier to continue to maintain GTK 2.0 than porting your app to a moving target like GTK3/4 with regular severe user and developer hostile regressions.

CADT would imply this kind of sabotage is not happening on purpose. There are certain parties that have keen interest in a severely dysfunctional FOSS desktop. It's more like GSAW (GNOME Saboteurs At Work).

Who funds this?

I would pay for porting back to GTK2.

This is of course a lie. They declare widely used APIs as "internal interface" and break backwards compatibility on a regular basis even on sub minor version updates.

> I admit, I do not understand GTK/QT development model at all.

It's very easy to understand.

QT is a commercial and de-facto proprietary product and the development model is: do what the paying customer wants.

GTK has no customers and after it was taken over by the GNOME crowd the development model is to deliberately sabotage the FOSS ecosystem. Small long tail projects can not afford to follow the relentless stream of backwards incompatible changes produced by upstream and die off. Even big projects like GIMP struggle with this. The result is a broken ecosystem which serves certain market participants (e.g. that offer desktop operating systems) very well.

Fog of war. You can't know what is happening. The only numbers I believe is the additional cost in $ and € the western taxpayer is burdened with. Because that is guaranteed.

These questions are irrelevant. The tactical significance of Finland to Russia is small compared to the resources required to invade it as is. Due to bad cost/benefit ratio it is therefore unlikely for Russia to attack Finland. But now that Finland is part of NATO it has to bear the cost when some other country gets attacked. It's a bad deal.

So who is the target audience of GNOME then? Does it even have users?

The EEE practices of Microsoft were a conspiracy theory as well until everything about it got confirmed as true in the Halloween Documents.

This also seems like misrepresentation of the entire file picker saga. First of all, it is absolutely laughable that something as essential as a thumbnail file picker is missing for that long, literally decades. Several patches have been submitted by people "willing to put muh effort and money in it" and got rejected because superficial idiotic reasons. On the other hand vast amount of resources are put into widely unpopular changes like client side window decoration, removing configuration options, turning everything into a tablet UI or breaking font rendering. And the "massive strides towards simplifying its codebase" means nothing more than dropping backwards compatibility on a regular basis while making everything more bloated and resource demanding.

Maybe Gnome is a project to sabotage the FOSS desktop. Stranger conspiracies turned out to be true. Personally I'd recommend: Don't use their software. Don't contribute to their ecosystem. Don't go to their conferences. Don't ever give them any money.

It doesn't matter if it is "opt-in". The problem starts with "built-in". KDE and Qt is very huge and highly complex software. Telemetry can be enabled or disabled without my knowledge, one update away. The same is true for your policy which makes it worthless.

Since KDE is shipped with build in telemetry now I can't recommend it to anyone. Opt-in or not, I've seen this game played before and it never ends well.

The biggest problem with GUIs is that there is no reliable standard that works everywhere. The VT100 standard is 45 years old and will most likely work for the next 45 years. It is dead simple to implement GUIs (just write to stdout) and all those programs that use that protocol to render their GUI are immediately portable to almost every platform on the planet and work over the network via ssh without any additional need for programming.