In my university, probably because the CS department at the time was an underfunded offshoot of the faculty of Mathematics, we basically didn't have access to computers (and I didn't have a laptop of my own).
We did almost everything on paper, even exams. I admit writing MIPS assembly on paper seemed strange to me at the time, but the effort you put in to put things black on white somehow made the knowledge stick into my mind more effectively. Some of that knowledge will stay with me forever, and I'm not sure the same could be said if I had taken "shortcuts".
I used to write code in a spiral notebook when I didn't have access to a computer. It was also hard to code on a computer in those days when the output device was an ASR-33, or a screen was 24x80.
This article has a weird tone. It directly criticizes the results of this AI-driven coding effort (which the author admits is of bad quality), while at the same time it tries to reassure the reader that they're not here to criticize the author of the PR.
not if they are different authors; AI wrote the code and the human the PR. These used to implicitly be the same person but this is something important we have lost. You've now got a smart, former developer in a position of power vouching for code they essentially didn't write.
So you're saying that the slop thus produced is not the responsibility of the human authoring the PR? I would assume it is, regardless of how it was produced.
It's not like the Shopify CEO intentionally tried to make something low quality. Was he out of his depth? Sure, but I don't fault him for trying. I think the people hyping up this event have caused more harm than the event itself.
Helix is my default, as it's a more mature/stable editor. I fire up Flow Control from time to time to follow how it's developing and for more casual editing. They both do an excellent job overall, but my muscle memory binds me to Helix for now.
(I know Flow Control provides Helix keybindings, but I haven't tried that yet and I generally like to retain the default behavior of an editor so that my user experience is more "portable" across machines.)
...What an odd and dishonest framing of the problem. Do you define "hospital not destroyed" as "some walls are still standing"? Because an easy counterpoint to your claim is the Al-Shifa Hospital, which you will certainly agree cannot be operational in this state and thus can be defined as "destroyed":
Okay, you go get treatment at that facility if it's working as well as you insist.
Besides, whether the facility is (partially!) operational today is besides the point. Your original post insisted that "Israel has destroyed no hospitals", while it clearly has. The picture I linked is from 2024. The fact that Al-Shifa was brought back to a partially operating state in late 2025, after months of partial ceasefire, doesn't disprove that it was destroyed in 2024. Sources like https://en.yenisafak.com/world/al-shifa-hospital-begins-reco... show that the situation is far from positive.
You said al Shifa isn't operational. I proved it is. Now you're trying to redefine "operational" to mean "yes, you can get treatment at the hospital but it's not working well." That's a major switcheroo.
I stand by my claim that Israel has not bombed any hospital buildings. If you think this is false, find me a hospital building that Israel has bombed, tell me when it's been bombed, the munition used, etc.
The quality of the benchmark code is... not great. This seems like Zig written by someone who doesn't know Zig or asked Claude to write it for them. Hell, actually Claude might do a better job here.
In short, I wouldn't trust these results for anything concrete. If you're evaluating which language is a better fit for your problem, craft your own benchmark tailored for that problem instead.
Great timing: I just received a Copilot spam email from GitHub. I don't remember opting in to such marketing communications, instead I generally opt-out from such communications as soon as I sign up to a service...
I came here to suggest the same! It's incredibly handy and I use it all the time at work: there's a process that runs for a very long time and I can't be sure ahead of time if the output it generates is going to be useful or not, but if it's useful I want to capture it. I usually just pipe it into `less` and then examine the contents once it's done running, and if needed I will use `s` to save it to a file.
(I suppose I could `tee`, but then I would always dump to a file even if it ends up being useless output.)
We did almost everything on paper, even exams. I admit writing MIPS assembly on paper seemed strange to me at the time, but the effort you put in to put things black on white somehow made the knowledge stick into my mind more effectively. Some of that knowledge will stay with me forever, and I'm not sure the same could be said if I had taken "shortcuts".
reply