@onatt0 The big industry mistake was factoring into thousands of functions in code, instead of just baking all that into a "protocol" of data structures in memory.

Source

• URL: https://x.com/NOTimothyLottes/status/1917661939469111373
• Author: NOTimothyLottes (@NOTimothyLottes)
• Posted: 2025-04-30 19:26:49

Thread

1/ @NOTimothyLottes

@onatt0

The big industry mistake was factoring into thousands of functions in code, instead of just baking all that into a “protocol” of data structures in memory. Like OOP member functions to load or mutate one variable = vomit.

2/ @NOTimothyLottes

@onatt0

I do all my custom CPU side stuff more like treating the register file like a “memory” of which the contents are aliased to different shared structures for different purposes across time

3/ @NOTimothyLottes

@onatt0

So the register file is more like an aliased global namespace. And “functions” are free of arguments and free of returns. This way of working with the HW is way better and easier than the ‘C’ model.

4/ @NOTimothyLottes

@onatt0

In the few cases where you need to reuse small code patterns, those end up a compile time macros that inline to different registers, larger patterns are already better factored to data

Related

• 2025-04-30-holy-truthnuke-and-people-think-c-is-the-optimal-state-of