It’s like a front backpack where the baby is facing the wearer and is supported up to the neck. Something like this https://share.google/cGaL54ZtqoxDq18zv

> If you think about it the war could have ended years ago and all the Ukranian/Russian lives lost could have been avoided if EU leaders were not so arrogant.

How exactly is Europe to blame for Russia continuing its war in Ukraine? Russia has clearly demonstrated a lack of interest in peace on any terms that could be acceptable to Ukraine.

One key frustration is it’s typically not possible to have an arm distribution that boots across most arm boards, because they have incompatible boot loaders. Ie you have a raspberry pi image and a banana pi image and an orange pi image and the rock pi S image that are all different from each other. There have been some attempts at UEFI on arm that would address this, but it’s nowhere near as consistent or compatible as on the x86 platform side.

What specific quality issues did you notice? I haven’t heard of any, but I wasn’t paying close attention at the time.

The Qualcomm models were faster. I’m not sure if they were better in low signal conditions.

The Intel models were worse, but they weren’t bad as far as I know.

> Snapdragon X2 Series is expanding to Linux, adding support alongside Windows and Googlebook

Is Googlebook a new name for chrome os? Or is it a typo?

They decided that instead of having an Android runtime on top of ChromeOS they would port the ChromeOS desktop features to Android. A Googlebook boots Android.

Fascinating. I did actually do a quick search and all the results were for google books, not a computer os.

A single board computer contains an application processor, not a microcontroller. They have very different design goals.

A microcontroller is a type of processor that offers very fast startup, predictable timing and direct access to hardware peripherals. In contrast to application processors that are intended to run an operating system, a microcontroller will not have OoO execution, multiple tiers memory (eg cache and dram). Usually they also lack an mmu and multiple privilege levels of execution (although that seems more common on riscv microcontrollers). All this means microcontrollers aren’t designed to run Linux (even if someone does figure out how to do that) or clock in the gigahertz, but instead provide very predictable low latency execution required for managing real time systems. For example they might need to operate a set of mosfets with microsecond accuracy to efficiently and safely control a motor.

> a microcontroller will not have OoO execution

Similar to a lot of old cortex-A soc.

>multiple tiers memory

The S31 also has cache and sram, with inpackage psram.

> Usually they also lack an mmu

The S31 has mmu.

I feel like you are deliberately misunderstanding me. I’m not saying that these define a microcontroller vs application processor, but rather that they stem from differing design goals. Presence or absence of features is illustrative not proof. All you need to do is look up what the A in cortex A stands for, or look at the data sheet of the S31 to see it is classified as an MCU by the manufacturer. I do admit that the feature set of this MCU blurs the lines somewhat at 500mhz with cache hierarchy and psram, but the ability to run from on-chip sram with dedicated performance budget keeps this from losing suitability for true realtime tasks.

Looks cool, but unfortunately doesn’t trigger the keyboard on mobile

Thank you for the feedback! I just tried on two iPhone and Android phones and it brought up the keyboard.

Ah it looks like the editor does, but the run screen does not. My guess would be since it’s emulating dos programs, probably the keyboard should always be visible.

Ah many thanks! Fixed it!

in the context of CPU performance / architechture `IPC` pretty much always means "Instructions per clock". That's a measure of the internal parallelism a given CPU core is achieving. Most of the time code is not able to get very close to the theoretical maximums a core can achieve for very long, so the numbers the OP is quoting are incredibly impressive.

I believe most of the 8bit microcontrollers from this era have no good optimizing compilers that get close to what competent practitioners achieve with assembly. I think it has to do with having complex addressing modes making the C stack fairly inefficient.

You are arguing against a very well known phenomenon. Technical people often avoid getting promoted to management precisely because they love doing the thing themselves. Despite the higher potential for impact in a management position, losing the detailed view of a practitioner is a real loss. This phenomenon is less obvious in big tech because there are so many people who really wanted to be managers the whole time, but had to be engineers first or never really cared about the work, but want a promotion for the better pay.