Completely agree. If this is a skilled Dev who’s built products like this before and you can build something like this in your afternoons and weekends in like 6 months without LLM tool assistance.
With basic assistance you can definitely cut that time down to 4 months or less easily.
And if this is a full-time project, you can probably get it out the door in 1 to 2 months with llm assistance. (Not vibe coding, two very different things)
I’ve built projects of the size in 5-7 months before we had LLM or ML coding tools.
With tabbed completion (Which most devs enjoy), and before full LLM code gen, 4-6 months.
With llm assistance, not vibe coding, it’s possible to build projects like this in 1 to 2 months without sacrificing quality or safety. If you are an experienced engineer and have built projects like this before. A lot of these are boring, boilerplate, stuff.
So the time spent doesn’t necessarily say that it’s vibe coded but if this is an inexperienced engineer then it very well might be and may be full of holes and issues.
Yeah, it should balloon out to 15TB or more I think
It’s literally says in the link. Go to the link and it’s the title.
Really with they would take security vulnerabilities seriously 😞
Because they are significant, and broad reaching.
How does organization work out?
We have dozens of workflows for our monorepo CI/CD stuff. GitHub organization with the flat structure is incredibly annoying.
GitLab is a single file?? (Or am I misinformed? )How does that work out?
A lot of that pain can be reduced by writing and running your code locally before pushing it to a CI environment. Generally with our automation we write a CLI, And GitHub actions is just an execution environment that calls the CLI.
And if what you’re trying to do must execute inside an action. You can run workflows locally with docker!
GitHub Actions mostly.
The rest is usually plumbing and code to support it. The actions are just the automated execution environment.
Is it cynicism when it’s the reality around us?
I disagree.
I don’t necessarily know about new music, artists, or genres. I want to get a mixture of stuff I haven’t encountered.
Something like 60% of the music I listen to in a given month I had never heard of 12 months prior. I’ve found so much music that I vibe with by way of generated playlists.
Discovering something new that scratches my music itch is in itself a pleasure for me, and I can go back to it at a later date, like everything else.
This doesn’t mean I support Spotify, but it does mean I disagree with your stance.
Not a single one of the robot vacuums that I’ve bought in the last 2 years seem to be able to function without internet access.
It’s asinine.
Also they break down so freaking fast. It’s not even funny. Even worse when the part that’s broken is non-replaceable and it’s like a $3 part.
Development time and user support?
These are two pretty obvious reasons. It takes time and time is a limited resource. Therefore, time should be spent on solving impactful problems. Lemmy account login is extremely low impact, it’s not a bad thing, it’s just not something that improves immich for a large portion of its user base.
Another thing is user support. Since the many instances are self-hosted for the most part, and they will go offline, and they will go away forever in some instances. Users asking for support for this login type and asking for additional features to make up for this baked in instability.
Essentially. Low impact work that may drive a higher volume of support efforts.
It’s the same reason some niche projects stop supporting Linux. Low user volume and disproportionately high “neediness” of those users.
Does it support multi-tenancy?
For instance, being a backup and media manager solution for multiple people in my family hosted on one server.
The same with a few friends that want to get out from under Google’s thumb.
I mean, yeah, probably all of these things.
But I wasn’t facility. I was a student.
The dorm itself did not have internet and had no plans of running ethernet or providing internet to students.
I got internet through a wireless access point, positioned very carefully in window for a WISP. And they distributed that to rooms near me.
It’s old magic too and in a pinch it works reasonably well.
We use this as a networking option for an old dorm I was in which didn’t have ethernet and the concrete walls between rooms made Wi-Fi unusable.
Blocks of rooms were not separated on different circuits which made this possible
Not exactly ideal archival software…
It doesn’t store files in a human readable way and requires a separate DB and application to interpret your stored data. Without controls over how it stores that data.
There’s a big difference between desktop environment needs and headless server needs.
Anything with user interaction will require an enormous number of additional services, which consumes resources.
I expect to run simple headless software on 256-512 MB of RAM. For example.
I love that MasterCard is pushing this shit under the guise of “brand damaging” products.
Yet this whole fiasco is the most brand damage they could ask for.
Dude, my team members put out code that’s like this or worse on a regular basis that gets caught in PR review without using AI tooling…
I’ve supported legacy projects that of course were built without tooling that didn’t exist. That are structured and written in ways that are far far worse than this.
Nothing here screams vibe coated.