Wasn’t the vim maintainer similar dismissive of the community for like a decade before neovim forked and rewrite the entire plugin layer and async layer?
Even with problems things could have improved.
Autocorrect hates me, I am sorry.
Wasn’t the vim maintainer similar dismissive of the community for like a decade before neovim forked and rewrite the entire plugin layer and async layer?
Even with problems things could have improved.


Probably not a lot.
My system idles at 3gb.
But then I do AI stuff and it needs 15-80gb. And I do data analyses that can use a lot.
Good code has always been about simplicity, taste, and understanding.
If a human provides understanding and taste, they can elevate AI code to be good.
Likewise if an AI isn’t well guided it won’t understand, has no taste, and will generate overly complex code. AKA Slop.
It feels like there’s a meta-discussion to be had about AI disclosure and AI use in a lot of these projects and it’s starting to boil over.
I would suggest that maintainers should:
When it comes to existing projects that start adding AI contributions it’s always going to be difficult. It’s not something projects started with even the option of, there’s no way to get consent from your users (nor consensus on whether you should you get their consent), and there have been varying levels of AI code gen for years now from simple completions to now agentic vibe coding.
I’ll be honest, most of my own projects use AI generated code, and I use it for work. It’s never code I couldn’t have written myself – because if it were how could I review it? But the fact is, in the year 2026 AI code generation is both fast, usable, and it’s near ubiquitous. There are tasks I could work on for weeks that I can build plus review in a couple of hours with AI. It’s very hard to argue with that, and I’m a very picky coder+reviewer with a full time job.
And lastly, for the community we all need to be mindful of open source maintainers.
They work hard, for free, and get treated like shit by users, the law, and big corporations. There’s a new generation of people who sign up for code hosting services just to request features or complain in your git issues, they’re opening up slop PRs and emailing you. Plus, internet users love to pile on and harass people.
Please remember there’s (usually) a human made of meat at the end of the intertubes, and when 100s of people write mean/abrasive things it adds up. Nobody is perfect, open source devs are just trying to share and help.
PS for mods: I saw there was another thread on another app using AI that was locked as off topic, I am trying to be constructive in this comment, but if it’s off topic/too divisive I understand.
Don’t let perfect stop you from achieving good.
It’s not radioactive waste, it’s code. You can read it, write it, change it. Just like any legacy codebase it’s full of shit, and maintaining means addressing the specific issues.
I gotta spruce mine up, this is excellent.


Same, I wish I’d bought two. Or even one.


If you buy now you can still brag about missing the next price increase when South Korea runs out of helium for chip production in 2 weeks.


Remember that if you get an idea, fuck around, find out, and write down what you’ve learned: you’ve literally just done science. Well, with computers, so it’d be computer science, but you get my point.
Honestly it’s never been easier to start doing things, and doing things is very fun. Good advice!
Also, how is the author using 1password for credentials on server? They have service accounts now, but is there a better way than just always providing a credential when asked?


I am glad I bought 128gb of ram last year.
You can forgejo with a container index enabled, I don’t know if there’s a way to use that as a proxy for downloading containers though.
Gotta be honest, my home lab chugs along quite happily.
Atomic fedora makes it hard to break, and then all the services are containerized and managed by configuration and just files only.
When there’s an update to a service: just pull service. Firewall needs configuring: just firewall-reset && just firewall-enable.
The only flaky thing is a vpn that I run through glutan and I’m thinking of dumping that provider.


What is the learning/on-boarding curve for this?
I ask because my home folder has a giant just file I use to script everything. I feel like I’m 80% there to just migrating.
Whoever drew this got it exactly right.

I have compose and a justfile, that’s enough documentation for any project, right??