144 points pandemicsoul 1 hour ago 65 comments
ex1fm3ta 48 minutes ago | parent
jmyeet 40 minutes ago | parent
LLMs themselves are built from the sum of human output when almost nobody who created that got paid for the value they created.
So what I'm hearing is that we have a distortion that can be described in terms of the worker's relationship to the means of production?
I honestly love it when people when people discover socialism from first principles.
ericmay 31 minutes ago | parent
There's nothing wrong with people working on hobby projects for fun, regardless of how useful they may be, and there's nothing wrong with others taking that work and building upon it for their own purposes. That's the entire point of open source software.
If you find yourself upset that someone "stole" your freely given away work or is making a profit off of it or you yourself are not being "compensated" for giving away "free" things you're the problem here.
blamestross 48 minutes ago | parent
gwt4life 45 minutes ago | parent
jarym 38 minutes ago | parent
Gone are the days of commercial organisations using OSS as a marketing tactic to gain a base they later monetise. It worked, it was a tactic and no one really liked it.
Your options will be:
a) community led OSS - like Apache projects, CNCF projects, etc
b) some dudes weekend OSS project
c) commercial vendor, likely proprietary or at best ‘source available’
pwndByDeath 30 minutes ago | parent
komali2 25 minutes ago | parent
An open source project management software nips at JIRA's profit margins. OSM loosens google maps' stranglehold. The swath of FOSS crms delegitimizes Salesforce's per-seat cost. Most recent example is open weight LLMs driving a spike of fear deep into the heart of the current lynchpin of the American economy.
MIT license was a mistake. We tried to play by the rules of capitalists and the obvious happened: the capitalists exploited us. "Thanks for the free labor! By the way, we don't hire people that don't have FOSS commits on their resume." Google and Facebook, last I checked, forbid the inclusion of GPL3 code in their projects. Great! Let's make more GPL3 copies of their software so nobody has to give them money anymore.
II2II 20 minutes ago | parent
Once upon a time, people payed hundreds or thousands of dollars to acquire software development tools. Even those who programmed as a hobby would have to spend a fair bit of money if they wanted to grow beyond interpreted BASIC.
I'm not claiming the current situation is ideal, but open source has given us much more freedom to program.
rvz 45 minutes ago | parent
Even worse, most of open source is now majority slop and it is highly likely that they will be abandoned.
Xirdus 44 minutes ago | parent
Because this is the joke. AI agents didn't change who "gets" to write software at all, it's still the same middle-level and senior devs it's always been. The term is intentionally derogatory towards the people who think otherwise.
rishankg 44 minutes ago | parent
pwndByDeath 36 minutes ago | parent
pjmlp 41 minutes ago | parent
Rhetoric question of course, especially in the AI coding age.
mmorrell0 38 minutes ago | parent
toomuchtodo 31 minutes ago | parent
https://rainshare.dev/ enables using up your token subscription to help others with their backlog, for example. Code forge goes brrr.
rvz 13 minutes ago | parent
You cannot eat tokens.
toomuchtodo 12 minutes ago | parent
I’d much rather give my money to a small sustainable business or a coop versus a traditional enterprise producing and/or hosting software, whenever possible. “Shop local” sort of thing.
cheney_2004 37 minutes ago | parent
fork-bomber 32 minutes ago | parent
If the test schema passes and if your original articulation of intent was correct, then what you have is already very good. From that point onwards, it's the question of accelerating development by just reviewing the output of the LLM and getting it into the right shape.
The combination of the review of the output of the LLM and the review of the test schema and its output, that is going to be a lot quicker to do than coding everything from scratch with a proper design paradigm.
jmyeet 19 minutes ago | parent
I believe that train has sailed on this association.
mtswish 5 minutes ago | parent
Ericson2314 35 minutes ago | parent
ovnz 35 minutes ago | parent
pwndByDeath 27 minutes ago | parent
sreekanth850 33 minutes ago | parent
mithril_ 33 minutes ago | parent
Ampersander 32 minutes ago | parent
canelonesdeverd 8 minutes ago | parent
apitman 31 minutes ago | parent
ovnz 27 minutes ago | parent
mipo256 27 minutes ago | parent
schnevets 15 minutes ago | parent
...and there is still a place for the robot chef, but the ideal destination for this world of post-commodified-code is probably a sandwich or Stouffer's Instant Dinner: Cheap, reliable, flexible products that don't promise to be a human.
pydry 6 minutes ago | parent
In the meantime you are encouraged to eat the food it cooks but to take full responsibility if it poisons you or any of your guests.
Normal chefs sometimes poison you too but the most popular restaurants have thousands of happy unpoisoned diners who have all eaten the same dishes. For free.
barelysapient 31 minutes ago | parent
joshdata 29 minutes ago | parent
My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.
Now I've been seeing PRs like that, fixing annoyances, performance edge cases, or hypotheticals, across my open source repositories, and I don't have time for them. I especially don't have time to fix problems that probably nobody will ever experience, and yet they keep coming. I have not organized my life around triaging annoyances (let alone fixing them).
If the trend continues, I'll soon be forced to close repositories to contributions, or just stop maintaining the projects entirely. And I imagine that's the point a lot of maintainers are at.
cwel 22 minutes ago | parent
Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I find that is most often the case. But there is definitely an increase in the "performance edge cases, or hypotheticals" framing, where I am equally befuddled/too tired.
awakeasleep 21 minutes ago | parent
cwel 18 minutes ago | parent
kuriho 8 minutes ago | parent
matkoniecz 5 minutes ago | parent
I had repeated PRs for entirely hallucinated problems.
awakeasleep 21 minutes ago | parent
We need the equivalent of that for open source software maintained by people from before 2004.
tombert 17 minutes ago | parent
linsomniac 6 minutes ago | parent
AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.
Have the AI tooling do the heavy lifting of reproduction and benchmarking. One of my projects is fairly complicated and one user ran into some problems which he could describe the situation that caused it, but was light on any other details: my apt package cache was slow to serve the PHP update to his users. I asked AI to try to reproduce it: Set up a repo, set up different versions of my cache, have a client pull it, put an updated package in there, and have a client pull it again under different configurations. This could have taken me hours to do myself. AI did it with ~2 minutes of my effort.
>I have not organized my life around triaging annoyances
Then don't. AI can help with the triaging. Or, I give you permission: Close the repo for contributions. If you don't have time to maintain it, let people know, so they can fork or replace it. It sounds like your repos are already closed to contributions, due to lack of time/attention. That's fine, don't feel bad, just go ahead and make it official.
matkoniecz 3 minutes ago | parent
For me it was a bit useful but it has not offset even 10% of damage caused by LLMs
and is solving least important problem
matkoniecz 4 minutes ago | parent
As a maintainer of some projects: at this point I would appreciate far more useful review of already submitted PRs.
As long it is not blind copy-pasting LLM output. That would be highly obnoxious attack.
chasd00 4 minutes ago | parent
lifeisstillgood 25 minutes ago | parent
Open Source did an end run round that problem by producing
- better quality code, faster, and replacing the arguments over standards with a level playing field marketplace
As we are learning software has eaten everything but everything has not become software literate - there are hospital MRI machines that are only certified for windows XP. Our supermarket fridges think they are cheap IOT devices for teenagers bedrooms.
It’s going to take a decade or more for society to work its way through replacing all its devices (sewages plants are devices too) wit what is a software literate approach - secure, PKI, monitored updated and … open
No fucker will trust a fridge running a blob of binary - a complete SBOM and a repeatable build will be table stakes
And while we could wait for standards what is most likely to happen is each industry wakes up and starts to say “we want a beyond zero based approach, PKI setup this way, the builds are published and run here and publish the firmware”
Walmart might be thinking about this now - but open source will if we are senile be the backbone
And it will finally be funded as the answer is for industry players to fund the fridge-python api project, mostly by hiring the devs. Or the devs go full pococo and get sponsored
hypfer 22 minutes ago | parent
This reads like Hacktoberfest all over again.
What one person might find "annoying", another maintainer might've purposefully put there. Not all friction is bad, and telling people to go out, remove all friction and then report back to receive a pat on the head is probably going to end poorly.
This reads more like another attack on the commons than someone genuinely invested in FOSS. Which.. uh.. checks out when you check out the author.
__
Please do not take advice on how to interact with FOSS from anyone but the actual people building it.
If you fundamentally disagree, that is fine. You can become the person that builds their own thing and makes their own rules within that space. But only there.
apitman 22 minutes ago | parent
faangguyindia 21 minutes ago | parent
A very common project that most guys who find this "vibe coding" do is make a calorie tracker, so they ask Claude to build them a calorie tracker, then they add some data from an Apple Watch and Garmin. Now they believe they've built a "dieting app."
It's just funny how many of them actually take data from Garmin and an Apple Watch and add a bunch of activities to work out a "calorie burn of the day" and how inaccurate it is.
Apple and Garmin are not accurate for this, read this: https://macrocodex.app/knowledge/rethink/how-many-calories-d...
But very few of them actually bother to check whether their "calorie burn estimate" even works to achieve the rate of loss or gain they set.
Not everyone is "doing better with AI", many of them are doing worse, they just don't know!
komali2 21 minutes ago | parent
florieger 17 minutes ago | parent
pandemicsoul 4 minutes ago | parent
FinnLobsien 17 minutes ago | parent
But I don't think there's a big overlap between the people who could even name one open-source library and the people flooding the market with vibe-coded to-do list apps.
jph 13 minutes ago | parent
1. Friendly editor: Vix IDE @ https://github.com/vixide
2. Broader web UI: Lily @ http://github.com/lilydesignsystem
3. Smarter web service helpers: Axa @ https://github.com/publicprojects-io/axa
I tried many open source software projects before starting these, and I'm a longtime open source developer so I highly value all the work from people before me for vi and emacs, Daisy UI and shadcn, Rocket and Loco, and many more. These projects are all aiming for public nonprofit social good.
deepsquirrelnet 7 minutes ago | parent
Lots of people make things now and that's cool and fun. But what people want to see is a track record of support. They want to know that the things they come to use and depend on won't exit the scene just as quickly as they came.
This is just like 'killed by Google' on steroids. Yes you can write way more things things than before, but if you can't sign up maintain them, then they aren't providing value.
Focus is becoming the commodity. Doing one thing really well is what becomes hard when you could be doing 1,000 things (poorly). To be successful, you can't just throw shit at the wall and see what sticks anymore, because nothing is sticking that way. The walls are already covered in shit. You have to have good product taste and a willingness to apply yourself to it for a long time.
x3haloed 7 minutes ago | parent
The fact that free software is benefitting at all from more coding power is a win. We have bottlenecks to solve though.