How does it deal with pointers if everything is stack based? You can't really return a pointer to something on the stack because it could get overwritten between when you return it and when you access it.
I've been working on a SDN software for mikrotik routers (and wireguard, etc) and Fable dies when working with any kind of wireline protocol or potentially implementing any authentication mechanism.
It's too the point where I just stopped using it. If you do generic stuff, it's fine. But the second it tries to start debugging protocols (which may include auth) that's where it begins to fail.
If you think AI is bad, wait until I tell you about the horrors of social media who profit on controversy and division, US health insurance which profits on rejecting claims, and big pharma profiting on the opioid epidemic.
And it's not like this is new, either. Upton Sinclair was writing about this stuff a century ago with books like The Jungle.
The only difference between then and now is we "think" we're not evil today. We've lied to ourselves that "We're so much better than we were back then." Facebook wanted to bring people together originally, but they ended up providing the most toxic social media experience known to man. Facebook forgot to tell us they cared more about profit than people.
Please spare me the argument AI is the straw to break the camel's back here. The system has been broken a long time before that.
I have list of issues with SQL. Not composable. Unable to detect query errors at compile time because the schema is only loosely coupled to the code base. And as you yourself point out, SQL is not standardized, which is also terrible and leads to things like Oracle vendor lock in.
And frankly this list hasn't changed in 30 or maybe 40 years now.
And DBA's were so notoriously egregious that Martin Fowler made his "NoDBA" blog post over a decade ago now. And the movement to NoSQL definitely made things worse.
I wish the SQL community would stop treating ORM's like the vietnam paper did 20 years ago, and embrace them for what they are, as a stepping stone, and maybe as a useful tool to help people understand SQL itself.
More likely they'll convince congress they will need their own. Only it will 20-200 times more expensive and the US taxpayer will be paying for it but won't get access.
Honestly those are used as weights now in some kind of obscure calculation (or maybe not so obscure calculation but I still don't understand it).
What I really learned during that time is that mail servers have well known IP addresses and reputations. And you can say all you want SPF/DKIM fixes that, but the reality is when google sends your email (even with your custom domain) it gets received.
Honestly, I think the biggest enjoyment I got from this thread is that programming culture is often toxic in ways that people aren't really ready to admit on this site which is dedicated to computers and programming.
I can hear them now: "Surely, you can't be happy with your decision, Mr. Ralo. You're leaving so much money on the table!"
Have you thought of opening your own truck repair shop? Often there are places where trucks break down and the solutions are slim to None. A good repair shop in the right place might make decent money.
I did that too years ago, but the management of it was kind of annoying. DKIM was just getting introduced when I stopped using it. SPF had controversy. I understand both of those are awesome now.
The biggest issue was if your ip address got listed in a RBL (Realtime Blackhole List), and then nobody would talk to you. Some were easy to get off, others were permanent blocks, and I found those to be constantly interfering with the delivery of mail. At least the rejection would usually tell you which RBL blocked you.
The more and more rude interactions like ghosting we have, the less human we become. Relationships become transactional instead of meaningful. On the other hand, talking to people as humans and leading with your humanity first makes you a better human.
I was writing MCP servers, now I just write tools for agents to consume. It's often easier to simply write the tool you need and suggest to it to look at the tool to do that thing.
I was also surprised to find out Claude knew how to use the gitlab api with pointing it at the token var in the environment. But for corporations it might make more sense to use a cli to keep the secrets separate from the agent.
I've been in the process of cutting the DC side of power bricks and crimping anderson power pole (APP) connectors onto both sides of the wire. For camping and ham radio, it's really nice to hook up to a battery without the AC inverter taking DC -> AC and the power brick sending that to DC again.
The only thing to be careful with is connecting different voltages to different connectors, but it's at least possible with the APP connectors to "Build your own" with different color housings and different ways of combining the housings.
So maybe 13.8v is red/black and something that's 5V is black/white, etc.
There was a point in the 1990's where microsoft word wasn't truly WYSIWYG. IIRC it was like an infinite page and the line breaks and page breaks were "estimates"
Further many docs from that era are plagued with abandonware.
TeX did one thing well for an era when often the only interface to the machine was over a Xyplex terminal server connecting to a tty at 9600 baud.