Very cool! I did something similar using Dolphin and LLVM, 16 years ago during my masters, for a course on virtual machines. I compiled the interpreter to LLVM bitcode and then used it that to build basic blocks. It was super slow, but it worked, and I had lots of fun working on it.
These folks have no lasting moat and they know it. We are still close to the November 2025 inflection point, so they had a clear advantage during these past few months. That will soon fade as open-weights models become really good, which is arguably already the case with DeepSeek V4.
I find it surprising that the word "incident" doesn't yet show up on this page. Cloudflare had at least two nasty incidents a few months ago. It certainly shook my confidence in the company's ability to run its infrastructure.
> and the GPL would prevent outright exploitation by our competitors, but those were to allay fears of my partners to allow me to make the gift.
I can understand his stance on AI given this perspective. I have a harder time empathizing his frustrations. Did he also have a hard time coming to terms with the need for AGPL?
I just read the article and I didn't get away with that rationale. Now, this isn't to say that I agree with the author. I don't see why go would *have* to add typed error sets to have a try keyword.
Yes, mimicking Zig's error handling mechanics in go is very much impossible at this point, but I don't see why we can't have a flavor of said mechanics.
Totally. I was in the ER, hitting my head against the wall because of the pain. And when the doctor cut it open... it was so painful, but the almost instant relief was worth it.
I have a very similar story. It went from ibuprofen and water to antibiotics the following day, to different antibiotics the next day, and finally to having my tonsils purged (i.e., cut open) with local anesthesia in 4 days. By this time I no longer could speak. It was the most pain I felt in my life.
I still trust doctors, but this made me much more demanding towards them.
Depends on the software. IMO, development speed will increase, but humans will continue to be the limiting factor, so we are safe. Our jobs, however, are changing and will continue to.
>WCET ("worst case execution time") is an important consideration: Operations should take a fixed amount of time and the produced machine code should be predictable.
Good luck. Give the avionics guys a call if you solve this at the language level.