In a third list of three things, Claude mentioned that this program does not link an HTTP stack. Good to know, I guess, but how can we evaluate it against Zawinski's law without knowing whether it can read or send email?
So in 2026, it is more efficient to waste thousands of tokens on rolling your own slop version, rather than adding a feature to something that already exists.
Something like btop has been there for decades and will continue to do so where as this slop tool will be unmaintained or even deleted in a year.
They don’t accept vibecoded PRs and yes, it’s much easier to sit for a evening or two than to wait for maintainers to review PR in a month and wait another month or year for release.
I’m not happy, but that’s the reality.
Erm, the based employees at Anthropic don't read their code before merging, they just have Claude read it twice. Why would I waste my time reading code when I could be proompting?
This is nice, however why build this when you could have raised a PR to btop to add support directly into it?
Perhaps because it's easier to reinvent the wheel nowadays?
From the btop contribution guidelines:
> "Vibe coded" PR's where it seems like the author doesn't understand the generated code will be dismissed.
If you don't bother to write your own announcement, I don't bother to look at your thing.
Please, please, take the time to write READMEs by hand. It at least shows intentionality.
No mention of Rust in repo description and every 4 sentences?! Thanks, I’ll look at it! I didn’t know I miss those things until reading README ;(
I hate this "witty" Claude speak where it tries so hard to be cool:
>I haven't seen yours yet
>, in the terminal you already live in
>truth
>Everything is optional
I can't really put my finger to it why, but type of writing pisses me off so much.
This + when it constantly leaks prompts and implementation details. E.g.:
>No sudo, no telemetry, about 1.3% of one core.
You just know the prompt the author sent. And of course the absolute classic:
>No ps, no powermetrics, no scraping.
In a third list of three things, Claude mentioned that this program does not link an HTTP stack. Good to know, I guess, but how can we evaluate it against Zawinski's law without knowing whether it can read or send email?
> I built
> > I built
I assumed it was Claude taking credit for it since it wrote the whole post anyway.
Me and my French mate Claude
Geez even the literally 1 line "about" is written with AI. What do people mean when they write "so I built..."?
So in 2026, it is more efficient to waste thousands of tokens on rolling your own slop version, rather than adding a feature to something that already exists.
Something like btop has been there for decades and will continue to do so where as this slop tool will be unmaintained or even deleted in a year.
They don’t accept vibecoded PRs and yes, it’s much easier to sit for a evening or two than to wait for maintainers to review PR in a month and wait another month or year for release. I’m not happy, but that’s the reality.
I believe btop was only released in 2021.
htop was released 2024 and top was released 1992.
I agree that the bar is much lower now, but reinventing rather than adding is not a new thing!
I assume 2024 is a typo, htop was released in 2004
What! Htop is newer than btop?
These descriptions are borderline insulting
> No sudo, no telemetry
Does it also not nuke your kernel? does it also not inject a keylogger? How will I know if it doesn't tell me! /s
You could just read the code.
Erm, the based employees at Anthropic don't read their code before merging, they just have Claude read it twice. Why would I waste my time reading code when I could be proompting?
hello