Need help?
<- Back

Comments (164)

  • joshdata
    > Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.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.
  • timbert
    I think we need a new model of software delivery.Here's my most-recent real-world problem: I wanted to plug in my midi controller keyboard and just play a piano, so I can practice my choral music. Very basic.This turned into many hours over several days trying multiple DAWs, trying to get tehm to install, get them to run at all, get them to recognize my controller, get them to play a VST plugin...changing system settings, completely jacking up my sound, restoring it all again.It was a nightmare.So instead I fired up Claude, worked with it for about 3 hours, and now I have an *8-channel* VST player that supports all my hardware, and includes a snappy UI, with outstanding performance and sound. It's amazing!I literally spent less time creating a custom solution than I did trying to get the off-the-shelf stuff to work. I could make my player OSS too, but the effort to do that is huge, for all the reasons this forum would understand.Bespoke software avoids all of that and allows me to do what I want, with the environment I have. I don't have all the features of an FL Studio, but I have what I need, and that works for me, beautifully, at low cost and effort. What's not to like?So maybe we should share OSS "templates" instead of full products, projects that are the barebones of a solution that you can clone, and have your LLM modify to suit your needs, on your platform of choice.For example, perhaps my barebones VST player is mostly good enough for you, but you also want to play sound fonts? Cool, clone my project, instruct your LLM to add sound font support, and add support for your controller or your output device. Or convert it from Gnome to KDE.The time and cost of doing this is so little now, why not? I'm getting more out of my computer than ever, and I'm happy about that :)
  • linsomniac
    > Pick one open source tool you use. [...] Spend a weekend fixing itBeware: Your best path forward there may be, contrary to part of the thesis in this post, be to vibe code a replacement. There are a couple reasons why:Expect to encounter significant push-back due to AI contribution. For example, I've had bug fixes to significant problems be rejected because "we are in the future going to be adopting a no-AI policy". Annoying because I spent my time working on it because they did not have a no-AI policy. Amusing to have another contributor contribute the exact same fix, like character for character, under a new PR (referencing my issue, so not done in isolation) and get it accepted.There may also need to be sweeping changes to the project you are fixing -- which are going to be a burden to the maintainer and likely wouldn't be accepted because of that. A fork may be the way to go here, but also "vibe coding" a replacement might be the best option.Earlier this year I build a replacement apt cache called apt-cacher-ultra. Part of it was because the existing apt-cachers had reliability issues, but a bigger part was I wanted something that would survive ubuntu.com being under a DDoS for a week or two. apt-cacher-ng was totally useless at that. The path I wanted to try was to have verified known good snapshots of the upstream, background refreshes, pre-fetching of known "hot" packages when the upstream refreshed. HUGE changes.I've put 100 hours or more into this "vibe coded" alternative (mostly enhancements and fixes for other users use cases). I'm pretty confident that this wouldn't have been something the apt-cacher-ng or apt-cacher maintainers would have been interested in accepting.
  • poisonborz
    Rarely do I see such a stupid headline on HN. I know where this comes from and I can sympathize with the author but from his subjective narrow experience he draws the wrong conclusions.People post a bunch of throwaway microprojects. So what.There are wide fields, industries, branches of society, communities, groups of friends left without proper apps to do "that thing". Not to do it better, but to do it at all. It is incredible that a much wider amount of people can engage in creating those apps now. That should be encouraged, and not gatekeeped into existing projects that are already drowning in PRs.
  • delichon
    Many apps have just been obsoleted by the new tech. I've tried hundreds of food logging apps and written a few. But none are nearly as good as my current daily driver, a Google spreadsheet wrapped by a GrokBot. I just tell it what I ate two or three times per day, voice or text, no attempt to normalize units or food names. It does all of that with nuance and I seldom have to correct anything. Major new features, like deriving a shopping list from the log, cost one short prompt. Or a running commentary by GaryTaubesBot.This was just a sci-fi dream in 2022. Now I wonder whether apps are collapsing into an inference wrapped singularity.
  • shmolyneaux
    > I help progressive nonprofits with their tech for a livingThis is the primary perspective behind this post, and that's going to look much much different than the devops roles a lot of us have.> Too many apps need a database, a cache, a background worker, a reverse proxy and a long config file before you see a login screenThese apps need a database/cache/proxy/config because creating a fault-tolerant, performant, flexible system needs these things. The author wants everything to be a single binary running on a $5-a-month server. A lot of these open source tools could be updated to run in this mode, but that's not the configuration that's sustainable when there's a disaster.You need to look at why these nonprofits are using open source projects in the first place. They probably want something free, and they probably want something with clear documentation. Maybe it's something that they're already used to. I would argue that AI-assisted (or vibe-coded) apps are cheap enough to fill this niche. Documentation is less important if the features of the app are much more narrowly-scoped. If they're already used to another app, then the vibe-coded one could be designed to provide a similar experience.I've worked with non-profits that have struggled under the weight of the software they're using. Most often the problem is the software being too general in a way that doesn't model the domain well. Cheap custom software would help a great deal.
  • gortok
    If a project ever has a hope of being sold (“Licensed”) commercially, open source is a death knell. In part due to the AI “training”, and in part due to how easy it is for larger actors in the space simply to take the code and do whatever they want with it.The problem with Open source presently is that it provides no way to sustain the energy used to support it. I have a limited amount of time in my life; I currently spend roughly 1/3rd of it supporting my family. If I use another chunk of time to ‘support’ open source, I’m looking at my work being taken and used for the profit of others without being able to profit from it myself. If I can’t profit from it, I can’t use it as leverage to make it so I don’t need to spend 1/3rd+ of my life working to support my family.I am currently writing software with the expectation to sell it. I may even give away copies of it, I haven’t decided yet, but the source code won’t be online, and the support documentation will be behind a registration wall, as will the API. Nothing will be visible on the public internet, not for any other reason than AI scrapers and the large companies that use them.There may be other ways for small software businesses to be sustainable, but at this moment it’s hard to see them.
  • gwt4life
    I agree but open source needs to solve the monetization problem; developers need to eat.
  • listenfaster
    I feel like AI has removed bottlenecks to me being able to contribute to open source projects, and the author is spot on with the “don’t be a jerk about it “guidelines”. Understanding the social element, the community function around maintenance of a project is a different ball game every time, and for me has often been its own research project. I remember before AI killing hours figuring out where to start in understanding mame, csound, and other older projects that have had many many different contributors, and weren’t the most welcoming to newbs. Now I have an assistant to ride shotgun with me while I figure out where to contribute, and can focus on whether my contribution is useful. I have this picture of a world of small functioning tribes suddenly being inundated by nomads who wanna join up.
  • cheney_2004
    Whats wrong with the term vibe coding? If it has a negative connotation, the problem isn't the choice of words, the problem is the software being produced. Rather than change the name, try and figure out how to raise the bar.
  • kaishin
    I build my own apps in order to solve real world problems I have. I don't see myself opening random PRs in OSS repositories only to get most of them rejected or ignored.
  • jstanley
    Typically open source projects will not thank you for your contribution and will instead be annoyed with you for bothering them.Yes fix bugs and add features etc. for your own personal use, but don't get your hopes up about contributing back, it's usually a waste of time.
  • ValdikSS
    We need to invent new definition to what many people expect when say "open source". Maybe use "Stewarded Open Source" coined by Dries Buytaert.https://dri.es/license-only-versus-stewarded-open-sourceThe truth is: open-source doesn't come with any support, maintenance or feature request fulfilment by default.By definition, that's just a code with no strings attached.Do not expect maintenance or bug/security fixes by default from any project, unless stated otherwise, or there's at least some metrics which hint of maintenance.We need SOCIAL.md to describe expectations from this project.If that mindset is new to you, read this: https://raccoon.onyxbits.de/blog/bugreport-free-support/
  • cush
    We probably need more apps with fewer features and more bespoke apps for specific domains rather than having businesses cobble together a dozen SaaS offerings.
  • _nobody
    We need more apps. Specifically, everyone should have complete ownership over their own software, so either people learn to build it themselves or truly own the tools they use, instead of renting it via subscriptions or losing control over it by the whims and fancies of c-suites, who brick the software which we paid for.
  • maxdo
    Alternative view : for security reasons open source use will shirnk, since it's becoming most dangerous vector of attack.Future Software Factories will have extra large static harness, that will be have a very few dependencies, e.g, reactjs, bundled into the package. Even nodejs probably will be more of a runtime feature, patched by the cloud.open source was mostly a feature of not enough software eng resources. Now , since this is in abundance, instead of a shortcut it becomes a risk.
  • jph
    Better open source can leverage better ways to learn and contribute IMHO. I'm working on building blocks for open source projects, using comprehensive code annotations to help developers learn, experiment, fix, and remix. I welcome help, advice, criticism.1. Friendly editor: Vix @ https://github.com/vixide2. Broader web UI: Lily @ http://github.com/lilydesignsystem3. Smarter web service helpers: Axa @ https://github.com/publicprojects-io/axaI 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 working on vi and emacs, Daisy UI and shadcn, Rocket and Loco, and more. These projects are all aiming for public nonprofit social good.
  • meerita
    That's not possible. Somethimes, the open source projects take a path you don't want and they don't want. So you have to build yourself the version you want.
  • FinnLobsien
    I agree that this would be a great thing.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.
  • coretx
    We need less apps with over 9000 functions and more that do just one thing right.
  • royraghav28
    We need apps. Apps monetize to survive. If big enough, someone comes along and aims to solve it for free.It's a cycle which breaks without either component missing.
  • florieger
    https://jordankrueger.com/images/gallery/blog-better-open-so... Error: „Load cannot follow more than 20 redirections“
  • x3haloed
    1. It's a stress on maintainers. 2. OS projects often close their doors to AI. See point #1.The fact that free software is benefitting at all from more coding power is a win. We have bottlenecks to solve though.
  • Ericson2314
    That's why I work on Nix. Let's make everything easy to install everywhere.
  • mipo256
    I'm a bit worried that we're going to end up with a lot of vibe-coded, incompatible in-house solutions. Giant frameworks and ecosystems will probably still exist, but niche solutions, I'm not sure.
  • nadis
    Tangential to the core points, but I somewhat like the moniker "AI-assisted coding" proposed here over vibecoding.
  • rishankg
    Couldn’t agree less. We need to understand the way people code and make these things
  • Ampersander
    Large software collaborations between strangers on the internet are becoming impossible, because people just send in slop nowadays. It used to be that if someone had written a patch, they had spent some time thinking about the problem and had some level of understanding of what they were doing. Now people ask an LLM to do a contribution to a popular project and just send in whatever the bot produces. Free software is drowning in slop.
  • mmorrell0
    open source doesn't pay the bills.
  • Xirdus
    > People call this new way of building “vibecoding.” I hate the name; it makes a real shift in who gets to write software sound like a joke.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.
  • hypfer
    > Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.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.
  • faangguyindia
    Just because you can build something with the help of AI doesn't mean it even works the way you intended it to. At worst, you probably may not have the ability to actually verify if it even works.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!
  • micimize
    "Don't do an easy fun thing to make your life better or more enjoyable, do a hard tedious thing purely for other people's benefit for free," basically.When someone vibes out a new little todo-like app, they are usually thinking of exactly _one_ user: themselves. They get what they want with very low executive effort. That is what's so cool about it!Good Open Source contrib takes effort, they don't want randos slopping out PRs. Total apples-to-oranges comparison.
  • jmillikin
    > Pick one open source tool you use. Find the most annoying thing about > installing or running it. Spend a weekend fixing it, with the people who > maintain it. Then tell me about it. Flex: The most annoying thing is that it's written in C (and is therefore a pain to cross-compile), and it has a runtime dependency on GNU M4, which depends on gnulib (the GNU anti-portability library). Flex is currently being rewritten to be more complicated and worse by ESR for reasons beyond my comprehension.I had an LLM write an m4 implementation in Rust based on the POSIX specs, then fuzz-test it against GNU M4 until it was mostly the same (modulo all the regex bugs it found in GNU M4). Then I had an LLM rewrite Flex in Rust, using rust-m4 as an in-process library.QEMU: It's written in C, has a bunch of huge dependencies, automated test coverage that rounds to zero, their main contribution path is a mailing list that sometimes swallows patches, and the maintainers might ask for a risky patch to be made more risky before they'll accept it. I went through that process once for a few relatively minor fixes and never want to do it again.I had an LLM write a multi-architecture emulator with a JIT, high test coverage, and a device plugin system that uses WebAssembly.Busybox: Written in C, huge pain to build. I tried switching to Toybox instead but it's incomplete, the build system involves a pile of shell scripts that require Bash, not any other POSIX-compliant shell (including its own), and the maintainer's response was basically to tell me to fuck off: https://lists.landley.net/pipermail/toybox/2024-October/0095...I had an LLM write a replacement in Rust that has enough shell builtins to run an autoconf script from within a hermetic build environment, and its only build-time dependency is rustc.---You know why LLMs are so great? Because they save me from having to interact with open-source maintainers who intentionally choose to make their software baroque and their contribution process obnoxious.You want your project to be written only in ANSI C89 and built with Meson and accept patches only via GPG-signed email to a mailing list that silently drops HTML? Fine, have fun, an ASIC somewhere in Iowa is going to spend the next 3 hours letting me forget your project exists.
  • ing33k
    /s Sorry, we don't need more blog posts with AI generated images.
  • pjmlp
    Yeah, but then how one goes about making their Github portfolio that some HR require on their job applications?Rhetoric question of course, especially in the AI coding age.
  • apitman
    Software is like food. Up until now most people had little choice but to buy meals from restaurants. Programmers are like chefs. Most of them work as line chefs at restaurants. Some of them start their own restaurants. Some cook for friends or volunteer at soup kitchens. Now everyone can have a personal robot chef for $20/mo that acts like C3PO. I think we're going to have to rethink a lot of assumptions about what most people are going to choose when it comes to software now.
  • sreekanth850
    irony is that majority of the oss projects are funded by commercial software vendors. though there are exceptions.
  • edstarch
    Thank you Claude, I'll keep it in mind.
  • deepsquirrelnet
    I think what matters above all else is a commitment to maintain a product. In a world where writing the software is cheap, what I think we're seeing is that people mostly just want to know that it'll be supported.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.
  • jayd16
    I think the biggest issue I see is how cutthroat and selfish the industry is now. At least in the comments it's 100% about what the fastest way to serve yourself is and absolutely no care to share that effort or resources with others.You don't think it was easier to scratch your own itch instead of host OSS before AI? Of course it was.Gone are the days of the hippie techno revolution, I guess. It really is "fuck community, I got mine" and its sad to see.
  • deckar01
    Do omniscient beings need libraries? Can they not shake the indirection down to perfect, minimal instruction? Fork and know good work can be pulled.
  • ovnz
    I vibereported a few bugs recently. It's satisfying enough to spend 15 minutes on, and easy enough as AI is good at collecting all the details and proofs for you. Also, there's no feeling that you re-used someone else's code through an LLM.
  • blamestross
    LLMs are essentially intellectual property laundering as a service. Not how I wanted IP to die, but using this to get more quality content into open source and the good of the commons feels like a critical task for us to share.
  • barelysapient
    Open source becomes agent written software. Instead of sitting in a repo, it'll be behind a prompt / hydration spec.
  • apitman
    Once the dust settles, I wonder what percentage of open source projects will accept AI-touched code.
  • gsoff
    for now it’s hard to make money from a new open source project. people need money, so they can’t work on open source for free. many open source projects that make money today are older projects with an existing community.
  • junixx
    Do one thing and do it well.- Old proverb
  • komali2
    So far, many FOSS projects seem to be taking a hardline no-LLM policy, since they seem to have determined LLM tooling to be a net negative for their projects. I wonder if that's because of their nature as very large projects, or very public projects.
  • mithril_
    Without open source your average AI probably couldn't even write "hello world". We're going to get slop after slop if developer don't write good open source code anymore.
  • dankobgd
    best i can do is more slop on top of old slop
  • lifeisstillgood
    So there is a XKCD cartoon that basically says “14 different standards - let’s build one to fix it all … now you have 15 different standards”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 marketplaceAs 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 … openNo fucker will trust a fridge running a blob of binary - a complete SBOM and a repeatable build will be table stakesAnd 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 backboneAnd 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
  • dario_amodei
    no
  • rvz
    ...and who is going to be motivated to maintain all of those open source apps? You cannot fund all of them, and open source has an unsustainable funding problem.Even worse, most of open source is now majority slop and it is highly likely that they will be abandoned.
  • NiceWayToDoIT
    [dead]
  • ReDress
    [dead]
  • ex1fm3ta
    Most of those apps are nice wrappers of open source projects. We need better licensing to prevent those vultures from stealing community works.