10 ms·

Easy go where? It’s open source, fork it.

code-blooded 26d ago
I can't and don't want to maintain all software I use. I need to be picky. There's a big difference between putting money or time into a community of builders and learning in the process (myself or growing others) and maintaining a vibe coded project. That's why I want to know right away which projects are vibe coded so that I don't put any effort into them. You're free to apply different criteria to software you use, but we're talking about having information to make an informed decision here.
- necovek 26d ago
  I am actually hoping this is a future where it does become possible. At least on top of what is generally more-than-good-enough (Linux kernel, base GNU system with the compiler toolchain, basic desktop environment...). So I'd like to have fully reproducible builts for a dozen or two apps I use seemlessly integrated into my laptop and phone update mechanisms. And yes, my smart TV, router, ereader and note-taking apps... However, infinite forking also means harder to benefit from others' improvements.
  - code-blooded 26d ago
    I'd definitely be interested in moving towards such setup if I could reliably and easily accomplish it. There are already people who vibe code all the tools they need. Personally, so far I got best results by carefully selecting a small number of apps and devices with good track record and community around them (think Emacs that's been around for decades, but also KOReader, Linux, AntennaPod on Android and many others) and supporting those in various ways. I might vibe code an extension or config for the apps, but then I still understand what it does and why. AI is yet to change that. I use LLMs daily at work, but software maintenance remains problematic. Producing stable software in unstable times is actually what pays my bills. Edit: And yes - if you fork, upstreaming is a problem. It's unfair for original software maintainer to need to review, test and integrate vibe coded code.

I can't and don't want to maintain all software I use. I need to be picky. There's a big difference between putting money or time into a community of builders and learning in the process (myself or growing others) and maintaining a vibe coded project. That's why I want to know right away which projects are vibe coded so that I don't put any effort into them. You're free to apply different criteria to software you use, but we're talking about having information to make an informed decision here.

necovek 26d ago
I am actually hoping this is a future where it does become possible. At least on top of what is generally more-than-good-enough (Linux kernel, base GNU system with the compiler toolchain, basic desktop environment...). So I'd like to have fully reproducible builts for a dozen or two apps I use seemlessly integrated into my laptop and phone update mechanisms. And yes, my smart TV, router, ereader and note-taking apps... However, infinite forking also means harder to benefit from others' improvements.
- code-blooded 26d ago
  I'd definitely be interested in moving towards such setup if I could reliably and easily accomplish it. There are already people who vibe code all the tools they need. Personally, so far I got best results by carefully selecting a small number of apps and devices with good track record and community around them (think Emacs that's been around for decades, but also KOReader, Linux, AntennaPod on Android and many others) and supporting those in various ways. I might vibe code an extension or config for the apps, but then I still understand what it does and why. AI is yet to change that. I use LLMs daily at work, but software maintenance remains problematic. Producing stable software in unstable times is actually what pays my bills. Edit: And yes - if you fork, upstreaming is a problem. It's unfair for original software maintainer to need to review, test and integrate vibe coded code.