spiralcoaster
37 minutes ago
Actual title: I had Claude code up a diff tool in Rust over the weekend
My guess is this made it to the front page solely from the Rust boost.
iLoveOncall
21 minutes ago
That's just too funny, even the README is entirely vibe-coded and the label under the image doesn't describe AT ALL the content of the image:
> ~120fps scrolling a 37k-line package-lock.json — viewport virtualization + off-thread highlighting.
When it's a static PNG of an extremely small diff.
I'm flagging the post as spam, that's what it is.
kyle-ssg
a minute ago
Hey, actually there's a script that generates the screenshots so that I don't have to adjust them every time the UI changes. I do get 120fps with a 37k line package-lock, try it yourself if you don't believe me.
asadm
33 minutes ago
> I had Claude code up
What's the difference?
bdcravens
19 minutes ago
To some, it's less authentic. In my mind, it's like "building" a house, when the truth it, you orchestrated contractors who did the actual work. A different set of skills, not necessarily less impressive, but probably is depending on the audience. (In my example, you wouldn't want to shoulder way into a group of tradesmen and talk about your building prowess)
applfanboysbgon
24 minutes ago
The difference is that the resulting software is useless, buggy, unpolished, will only be used by the person who prompted it and only for about three days before they get tired of it, and that nothing was learned.
mathieudombrock
19 minutes ago
That's what I'm not getting about these kinds of posts. What is the point of sharing this? It's just a bunch of nothing.
kyle-ssg
19 minutes ago
Hey, actually my goal is to stop using my IDE, it'll be one less subscription for me. So I won't get tired of this, I plan on using it daily. I've spent quite a few years obsessing over software quality so I won't accept unpolished and buggy!
applfanboysbgon
9 minutes ago
Everyone who vibe codes something over the weekend thinks that their vibe coded software will be the greatest thing since sliced bread. Then they realise that as they continue prompting, it takes disproportionately large amounts of effort to see any progress as program complexity rises and the token predictor begins tripping over itself more and more. At least use it daily for a month rather than saying you plan to use it, then try showing it. If you could actually get through a month of using and prompting on the project without getting tired of it, that would already put you ahead of 99.9999% of vibe-coded projects. As it is, literally anyone could prompt for this over a weekend, so what value does showing this have?