I appreciate Ruby so much more now after writing a tiny Assembly + C Grub-compatible kernel and being forced to read libc source code.
The lower levels truly are a dark place.

I really want to make a pun about Elmish horror, but it's higher level :(

I write code for systems that don't even have an OS. The upside of working bare metal is that no bullshit is between my code and the hardware.

Luckily there exists cython for python

@Fast-Nop
Your implication of having access to standards-compliant hardware makes me jealous.

@Oktokolo What standards? There are just several hundred pages of manufacturer datasheets of the hardware, that's it.

@Fast-Nop

How do you write for system which have no OS? Don`t you need OS to run it?

@mr-user The processor has an interrupt table at a defined address, and upon reset, it will fetch the address of the reset interrupt from there and start code execution at that address.

That leaves only the question how to get the code in, and that's typically done either via a manufacturer installed bootloader with external interface, or with an in-system-programmer to flash the software.

@Fast-Nop
Uhh. Well, at least the manufacturer actually lets you read the documentation...

@Fast-Nop
They don't even erlang. Kids today 😭

@Oktokolo They have to - otherwise, they couldn't sell their stuff because nobody would design it into real products. You get also tons of application notes on how exactly to use this and that. Everything publicly available on the manufacturer websites.

Personally, I'm quite fond of the STM32 because there are tons of nice evaluation boards on the market that are good enough even for prototyping.

@Fast-Nop
The Linux graphics card devs surely are way more jealous than me.
I tried assembler on cheap PIC 8-bit µC. But the bank switching made writing code for it annoying. I still have it lying around somewhere but i didn't touch it in years.