Jajcus

Non-toxic glue would be starch or gelatine - both used as base of some ‘real glues’, both with valid culinary use, including exactly this use case. We just don’t call those ‘glue’ in this context.

Sounds like what happened to Kerbal Space Program 2… it didn’t end well

Didn’t they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver

Probably. And that is exactly what was expected from them since the beginning of their Linux drivers. Kernel is not a place for such big and proprietary piece of code. So this is the important change.

Yes, the driver is still proprietary, but it does not break the kernel any more the way it did.

But this is the part where being open source is most important. For security, maintainability and convenience reasons

One could even argue if the usespace part, the OpenGl or Vulkan implementation, is still ‘a driver’. (I think it is, at least partially)

Sounds like a mobster kind of favor. If that is true, then it sounds like Sony took advantage of Arrowhead weakness.

Deponia series from Daedalic Entertainment. The first two games are really great. The other two not so much, though.

Valve is the company responsible for unlocking my PC for gaming. Most games can now be played without using Windows and Valve is mostly responsible for that. Because most game developers do not care and would rather force you to use proprietary OS than let you use what you prefer.

Well behaving programs give control back to the kernel as soon as they are done with what they are doing. If they don’t the control is forcefully taken away after some assigned time.

It looks something like this:

Something happens – e.g. a key is pressed – a process waiting for this event is woken up and gets e.g. 100ms to do it stuff. If it can handle the key press in 50ms, kernel notes it used 50 ms of CPU time and can give control to another process waiting for an event or busy with other work. If the key press triggered long computation the process won’t be done in 100ms, the kernel notes it used 100ms of CPU time and gives control to other processes with pending events or busy with other work.
After one second the kernel may have noted:

Process A: used 50ms, then nothing, then 100ms, another 100ms and another 100ms
Process B: was constantly busy doing something, so it got allocated 6 * 100ms in that one second
Process C: just got one event and handled it in 50ms
Process D: was not waken at all

So total of 1000ms was used – the CPU was 100% busy
Of that 60% was process B, 35% process A and 5% process C.

And then that information is read from the kernel by top and displayed.

How does the OS even yank the CPU away from the currently running process?

Interrupts. CPU has means triggering and interrupt at a specific time. Interrupt means that CPU stops what it is doing and runs selected piece of kernel code. This piece of kernel code can save the current state of user process execution and do something else or restore saved execution of another process.

Not that easily and cheaply as they used to be.

Doesn't sound like the 'cheap small computer you can run your hobby electronics project on' that the original Pi used to be. It is not as cheap and a power hungry beast, still small, though. More and more like a PC and less and less a small cheap embedded platform. For some people it is a plus (I guess for most people here), for some not so much.

I tend to build my projects on Raspberry Pi Pico now, but sometimes I would need something more powerful and Raspberry Pi 5 will be too much.

In Poland: decimeters are sometimes used (I have been ordering cut sheet metal priced by square decimeters) , I have not seen decameters in use. Hectopascales are often used in weather reports. Decagrams are often used when buying food where these amounts make most sense (meat, candy).

The ‘more exotic’ prefixes are usually only used with some specific SI units and in very specific contexts.

Modern corporate management model is just broken.

Maybe the kettle has some kind of non-sticking internal surface?

Yes, that sounds like limescale.

Matrix is open protocol, everybody is free to build their own clients. Maintainers of any one implementation are free to choose code to include in their project. And people can fork Element if they don’t like the way it is going.

Maybe Element developers are not great in including external contribution… but still nothing else seems to implement Matrix that well.

No other client seems feature-complete. I wish I could use NeoChat instead of Matrix, but it still cannot even handle encrypted conversations properly. Are they rejecting contributions too?

Unfortunately they are all both recently. It seems pointless to be rude to a bot.

Sulfur polution actually has cooling effect, so it is kind of opposite of greenhouse gases. It sucks in different ways, though.

Jira was ok until they dropped self-hosting option. Why should I keep internal development data at third party server?

Other Atlassian software, though… oh, what a mess. And it only was getting worse with any new release. I am glad we have dumped it all.

That depends on tree species and damage.
Willow tree would probably survive that without a problem, most other trees won’t. Some could be saved with appropriate protective measures, like trimming the roots.

In enhances security by allowing high-entropy passwords to be easy to remember and write, so you have no incentive to use short/simple low-entropy (insecure) passwords.

The point of the attestation is to show that given browser won’t do some things. If the browser is open source on open source operating system the user can modify it in any way he wants, so not such attestation can be given to such browser.

Even if we are ok with attested browser being official builds never modified by users, then user could still fake it if they have full control of their operating system. So the operating system must also be attested, so it cannot be freely modified. And what is a point of open source then? You can see, but you cannot touch?