Vibe coding. Producing code without considering how we should approach the problem. Without thinking where exactly is the problem. This is like Electron, all over again.
Of course I don't have any problems with the author writing the tool, because everyone should write what the heck they want and how they want it. But seeing it gets popular tells me that people have no idea what's going on.
if the author knows what they're doing and understand the model of the code at least, i don't understand the reason mentioning that it was vibe coded. maybe declaring something is vibe coded removes part of the responsibility nowadays?
Someone once told me that their mistake wasn’t theirs, but rather it was ChatGPT being wrong.
I think you have a good point about why people say it was vibe coded.
It might also be because they want to join the trend -- without mentioning vibe coding, I don't think this tool would ever reach #1 on Hacker News.
HN guidelines say one shouldn't question whether another commenter has read TFA, so I won't do that. But TFA explains exactly why it was vibe coded, and exactly why they're mentioning that it was vibe coded, which is that that was the central point of TFA.
And why should they care what's going on ?
Do you care about your binary code inside your application, or what exactly happen, in silicon level, when you write "printf("Hello World")" ?
Yes.
I verify dynamic linking, ensure no superfluous dylibs are required. I verify ABI requirements and ensure a specific version of glibc is needed to run the executable. I double-check if the functions I care about are inlined. I consider if I use stable public or unstable private API.
But I don't mean that the author doesn't know what's going on in his snippet of code. I'm sure he knows what's going on there.
I mean that upvoters have no idea what's going on, by boosting vibe coding. People who upvote this are the reason of global software quality decline in near future.
All your stuff is still pretty high level compared to the pure metal inside CPU. Do you which register the compiler decied to use to store this variable, or does the CPU will take this execution branch or not ?
It's all abstraction, we all need to not know some low level layer to do our job, so please stop gatekeeping it.
What's your point? That we shouldn't care about anything at all because there is 1 thing we truly shouldn't care about?
That we shouldn't care about spending $1 for a sandwich therefore managing home budget is pointless?
My point is, you should care what you work with, and it's perfectly fine to not know the lower detail.
Different people will care different layers.
I don't agree to this, but even if we assume I do, then all abstractions are still leaky, so in practice it's often simply impossible to not care about lower details.
https://en.wikipedia.org/wiki/Leaky_abstraction
Not caring about lower details in the expert domain is simply carelessness. We also need to consider how the abstraction layers are merged and what is the outcome. Abstraction layers are a tool, they are not the immutable environment we are operating in.
Clients can have the luxury of not knowing what is in the details, but not programmers.