CTO at ProblemShared, PhD computer vision and machine learning, technologist, C++, system design, early stage investor, incl. @NearDesk & @TainaTechnology
Say what you will about Windows (OS), but the NT kernel really is an engineering marvel that still puts Linux to shame in many ways.
The quickest way to describe it for a programmer, is NT was more like an object-oriented language, with a strong security model from day one, whereas Linux is very…not.
A lot of the “good” features in Linux feel bolted-on (SELinux, Capabilities, Namespaces) because…well they were. I love to imagine an alternate history where NT won.
IMO, Microsoft *should* have made an “Open NT” in the early 2000s; not fully GPL-style open, but one where a large org could say…swap out a memory allocator for their own. (they sorta did this with limited source access, but it was too restrictive)
You could imagine say…an early Amazon forking OpenNT to create an “AmazonNT” for EC2, where they have a modified scheduler, network stack, whatever. But, the security+compatibility contract keeps a stable baseline on the Microsoft side.
Controversial take, but if we enter this era where users are giving AI agents increasingly higher levels of access control; the Linux kernel is legitimately a poor fit. Think about it; answer the question “What exactly is this AI agent allowed to do?”
On Standard Linux, it’s disgustingly messy with lots of overlap.
Do you use UIDs? GIDs? ACLs? CGROUPs? Policies? SELinux? Filesystem modes? There’s not a singular coherent graph of capabilities you can point to. Too many ways you can escape an initially narrow scope.
NT, by comparison, can go the route of explicitly typed resources, and then you could have these really strong centralized audit trails when an agent goes haywire…etc.
I know I’m rambling, but the point is…if you were greenfielding an OS kernel from scratch, in 2026, with the intent of being forward-looking, it would *not* look like Linux. Frankly, it’d probably look a lot closer to NT, or even a BSD fork…
Most home routers get installed by a technician once, and nobody ever opens the settings again.
One guy was paying for an expensive internet package, and Zoom still froze and YouTube 4K still buffered every single night.
His neighbor, the tech-savvy one on the street, spent 10 minutes inside the router's settings.
He didn't upgrade the package.
He didn't buy a new router.
He didn't call the internet company.
He changed 6 settings. That's it.
And suddenly, everything got faster, across every device: phones, laptops, the TV, even the smart doorbell.
Same router. Same package. Same house.
He told him: "Your internet was never slow. Your router's been running on the exact same default settings the technician left it on the day it was installed."
Here are the 6 settings he changed:🧵
(Save this before it disappears)
@thorstenball@robrhyne I’d like to see the agents understand they don’t know everything and prompt the user back, so software development with agents becomes collaborative. Also why have agents generate source code at all? If there's no human maintenance, they could directly generate optimised binaries
When investors or M&A underestimate technical risk, the consequences are not abstract; they show up in missed targets, stalled growth, customer churn, and emergency engineering spend that was never priced into the deal.
https://t.co/y2nlwJ2Yb3
🦞 BIG NEWS: We've molted!
Clawdbot → Moltbot
Clawd → Molty
Same lobster soul, new shell. Anthropic asked us to change our name (trademark stuff), and honestly? "Molt" fits perfectly - it's what lobsters do to grow.
New handle: @openclaw
Same mission: AI that actually does things.
Knowing how to write assembly is a skill you should learn, and these guys have a great resource for you!
I've debugged 10,000 lines of assembly for every line I've ever written... but writing assembly from scratch is a core computer science skill, I believe: even if you never use it.
Will you use it to write new code? Maybe not. But when you get dropped into a call stack without source code, at least you won't have to ask your Dad for help!
And the next thing you should do after learning to write ASM is to get a crisp understanding of what your C code actually compiles to. Like a switch() statement is often a jump table, but if you've never debugged one...
Everyone knows that the x86 ISA is big.
Modern CPUs have ~1000+ mnemonics. Guess how many make up 90% of compiled C/C++ code?
TWELVE. I'm not kidding.
The question is…what if we shrank it?
@tswain555@jasonvmiller I tried this in early 2000s and a 5+ yr developer. So-called principal rejected the code as unsafe and insisted it be wrapped in a strict to guarantee placement. I couldn’t be bothered to argue.