Comment by mikae1
4 days ago
And then you're also the maintainer of the software in charge of keeping it up-to-date with its dependencies etc.
4 days ago
And then you're also the maintainer of the software in charge of keeping it up-to-date with its dependencies etc.
> keeping it up-to-date with its dependencies etc.
not if the software is functional today, and doesn't require interacting with third party systems (like this tinylittleoffice suite).
By the time the underlying infrastructure (like browser compatibility, or self-hosting OS becoming obsolete) fails, you're likely no longer using it anyway.
The "documents" seem exportable in text format, and in any case, potentially salvageable with another vibe-coded tool if such need arise.
Therefore, the original author is no required to maintain it.
That's a rosy eyed view. users running outdated code not getting security fixes are sweet honeypots for modern automated llm-backed mass exploitation machine long before something obviously fails for you.
you'll be spending tokens on getting it maintained, and if you don't spend enough you get pwned by guys who do. who exactly is winning in this scenario?
"democratizing software"...
You're just criticizing FOSS software in general now.
4 replies →
Wild how LLMs both weaken software security and supercharge the attackers at the same time
3 replies →
I am placing your time of digital fruition in the 00’s or later? Not bashing, but we bought floppies in the 80s with software with no updates. Cool kids got their software from Oh No More Warez + keygen in the early 90s. That went online in the late 90s.
Always online, internet of shit and perma update crap came at that same time, first for the OS and later for everything. Oh, plus two decades of using shady Russian software for virus scanning. Shit went up, update everything became everywhere and everyday. Plus gigabyte frameworks for functionality that was kilobytes before.
My point in cursing too much? (Sorry, mentally screaming FUD here.) That tiny code projects, even without an active maintainer, in the LLM-era are probably a lot more secure when run by the people they target (we run containers, and sandboxes, the cool kids run immutable distros). This is democratizing software, and it has the great feel of old.
Please everyone, vibe code tiny project with tiny codebases everyday. Dump them on GitHub in a free tier. Make so many that the people have a free choice again! And go watch Cliff Stoll again for that hacker energy!
2 replies →
This is the part managerial and marketing types don't understand. Their expectation is usually that "since its a computer system (sic) the tech team will support it from now on".
patching dependencies correctly was one of the first agentic coding tasks llm solved 100%. you will need to dedicate a session once a year to to such patches. Or community of vibe coders will do it for you .
Use AI to maintain it.
AI doesn’t magically maintain things, you still have some human overhead.
Less and less human overhead with each model release.
You say that, and then here I am basically vibe coding SaaS for money right now lol
This is trivial now. It can even be automated. Literally just type “automatically monitor and maintain x” into Claude or Codex.
Vibe code it without dependencies?
No I'm not, Claude is
lol, paying a big tech company for tokens is not democratizing software
It is just like a power-tool. There are many vendors, interchangeable mostly. I'm democratized in drilling and screw driving.
but it is democratizing product creation.
No need for simple offline website stuff like shown here.
It’s not simple at all. Check the source: https://github.com/aboard-io/tinylittleoffice