Maybe they mean X11-screens. That are more or less independent screens, you can't move a window from one to the other for example.Emacs supports that somewhat with the "open new frame on display server" menu option, but usually, multiple screens are not very useful.

Nowadays, multiple monitors present one big virtual framebuffer and only one logical X11 screen.

It is a niche feature, but it is still used eg when an application wants to have good control over a screen's frame buffer to display sth in an external monitor and minimise disturbances. I think it is fairly standard in psychophysics experiments, at least with some software. That's where I worked with such a ("zaphodsheads") setup.

They are also roughly analogous to the modern DE concept of "Workspaces" which people seem to enjoy.

They couldn't sell those cars in europe.

the original question has a=, you have a+=

They're using the version from the top comment, not the post. It also switches the pre-increment to post-increment.

I was just replying to the comment ¯\_(ツ)_/¯

Not an expert, but AFAIK 450 is a non-permanent error that basically says "try again later".

They claim not only fast charging, long life and low cost, but also very high energy density, no degradation in low temperature, no thermal runaway, non-hazardous materials and no "geopolitical" needed.

I think it is safe to assume, given the buzz all around the donut battery, that VTT would immediately release a statement if this report was fake.

edit: https://www.vttresearch.com/en/news-and-ideas/donut-lab-comm...

Who else is paying the taxes if not the customer? Who else is paying anything if not the customer in the end?

Wikipedia article would be a good start: https://en.wikipedia.org/wiki/Tax_incidence

It would probably make more sense to target something like this https://www.hackster.io/news/andrew-bunnie-huang-prepares-th... with linux, has MMU and more RAM.

This one runs Linux on the ARM cores rather than the RISC-V cores in the same package, so it's apples and oranges, but still pretty neat for something that comes essentially with a companion MCU and is in the same form factor:

https://milkv.io/duo

In embedded systems it's very common to have a bigger SoC and a satellite MCU to handle e.g. network comm and power lifecycle. I've still not really tried out my Milk-V Duo, but it's interesting to get a combo like this in a hobbyist board form factor.

They also claim desktop-class performance for this RISC-V-based miniITX board, it's a bit weird though since it doesn't claim RVA23 compliance:

https://milkv.io/titan

I'm building Fostrom (https://fostrom.io), an IoT Cloud Platform. We have Device SDKs to simplify integrating devices, powered by a small Device Agent written in Rust.

I wanted to support RISC-V boards too, so I went with the Milk-V Duo S as the test device. I have managed to get Tailscale working, and our Device SDK works too, with the bundled Python.

The experience of using the Milk-V Duo is definitely not as straightforward as the Pi Zero, but it does work, and is easily available in most places, unlike some of their other products. The Linux distro they provide is quite barebones, and I wasn't able to get Debian working. The docs for the device are pretty decent. I hope we get better support for Debian/Alpine/Arch for these kinds of boards soon.

Availability is a major factor in projects like this.

Interesting. I sometimes get similar behaviour on KDE / wayland, usually it is "2" or "3", and it seems to only affect electron apps. Always thought it has something to do with a dodgy ps/2 to usb converter I use to attach my old mechanical keyboards. I think it does not happen if electron apps are started with "--ozone-platform=wayland" but not completely sure, and I have no reliable way to reproduce or somehow trigger that behaviour.

Aren't they talking about the c++ dialect the compiler expects without any further -std=... arguments? How does that affect the bootstrapping process? This https://gcc.gnu.org/codingconventions.html should define what C/C++ standard is acceptable in the GCC.

The way I read withzombies's comment (and it could be wrong) was they were talking about the language version of the compilers source. I assumed that from the "dogfooding" portion of the comment.

Correct, this is a discussion of which language version the compiler should follow if the programmer doesn’t specify one. It’s not about which features are acceptable when implementing the compiler.