> For me, the joy of programming is understanding a problem in full depth, so that when considering a change, I can follow the ripples through the connected components of the system.
100%. The fun is in understanding, creating, exaplaining.
Is not in typing, boilerplating, fixing missing imports, and API mismatch etc.
I'm still searching for successful vibe coding examples.
Each time I tried it, with custom rules, git, and all the best practices I found, it went amazingly well initially, and garbage afterward.
Using the same technique, after a while, it generates a lot more shitty code than helpful.
> So, it’s shit and you’ll spend a long time fixing it.
It just takes more time overall to make it functional.
Fixing, debugging and improving vibed code takes more mental resources and time than just writing it from scratch.
Also, there's the flow aspect. Each time you let it "vibe", you're losing the flow state that is important while creating and thinking about complex work.
>I'm still searching for successful vibe coding examples.
I'm wondering what this means.
Kind of by definition, you wouldn't be able to tell "successful vibe coding" from "successful coding", right? Unless someone announces it. And a quick look at the comments here, or any other thread with about AI & coding, would immediately tell you is a bad idea to announce.
There's a few things you just don't say on HN, because you'll be piled-on immediately: don't criticize Kagi, don't hint at being pro-cryptocurrency, don't announce you "vibe coded" something even if it's extremely successful, etc.
(The immediate downvotes on this is actually hilarious, and proves the point)
For frontend, I would go with either React or Vue, both with a huge community and already a lot of builtin solutions.
I would 100% start with a design system, maybe material UI.
Nothing fancy, low maintenance and painless onboarding/development experience.
Yeah...we know, but there is a plan of rewriting / refactoring some parts and we hope to port as much as we can from Python 2 to 3 by the end of this summer.
I accidentally upvoted your comment which is annoying as I think your attitude stinks. This is a useful project, what language it was or wasn't written in should be irrelevant. You'd already pointed out that it disappointed you, a pointless comment but fair enough, then you went on to rub it in further - was there a need for that? No.
I agree, the main page is a little bit outdated.
You can mount remotes with where you have only read access, gitfs will fail to push something on the remote, and will put the entire repository in read-only. Right now, you don't have a read-only option, but it would be nice to have :)
Great idea about tags and commits directories. It would be nice to specify at mount point, if you also want tags and/or commits etc.
