> 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.
> to fix problems that probably nobody will ever experience
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.
not the parent, but I received one PR adding a new feature to my and similiar projects at the same time.
When I questioned the use case the PR sat around until it was closed months later.
Hardly a real user.
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.
> 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.
For me it was a bit useful but it has not offset even 10% of damage caused by LLMs
rejecting a PR saying "i don't have the time to deal with this" is 100% valid thing to do. Don't let yourself be taken advantage of, it's your project. If the submitter doesn't like the answer then they an fork and go on their merry way, that's also a 100% valid thing to do and is the backbone of open source.
Just make a contributor license agreement based on Benedictine doctrine. At least one very successful FOSS project does that: https://sqlite.org/codeofethics.html
I reckon we’re going to see more proprietary software over the next year.
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’
Irony: the number of developers who rely upon other people's open source to develop commercial software or services.
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.
I work a job for my money that isn't developing and haven't yet developed something worth enough to others to consider making money that way.
If I did, I would consider a finite sum (e.g. kickstart) then release the code. I see software/digital goods as only scarce until they are released. So their value plummets to $0, its only nature defying legal structures that make it otherwise.
I don't think of open source software as a way for me to make money, I think of it as a way for me to prevent other people from making money.
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.
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.
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.
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.
I personally think that there's nothing wrong with vibe coding so long as there are as close to watertight ways, checks and balances to verify that the output is correct. And the best way to do that is to invest domain specific expertise in coming up with as comprehensive a test schema as possible.
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.
The term was defined to mean slop. If you are vibe coding you are not doing engineering. I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.
Vibecoding has come to mean "AI slop code" where the people producing it don't understand it, like at all. It can be poorly structured and hard to comprehend.
I believe that train has sailed on this association.
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.
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.
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.
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.
In its current form, it's a fundamentally antisocial technology (or at the very least is massively enabling antisocial behaviours). And there's no interest from its makers in fixing that. Hell, if you're a bit cynical you could say its working as intended.
Putting misguided effort into positive externalities is certainly a preferable outcome to misguided effort into wasting time (the true limited resource)
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.
That is definitely the case. I think what is clear now is that we're going to have a lot more in-house solutions. Cooking at home became easier. So that the restaurants have to be quite good at what they are doing, and still not every person will turn to them.
The robot chef routinely poisons people. When it happens it's considered to be a "user" issue or something that will be fixed one day soon. "It's as bad at poisoning people as it will ever be, it'll only ever get better" some people argue.
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.
But the robot chef is $20/mo on a special deal may rise to $400/mo after the trial period, is more resource-intensive than a human chef, and is one misconfigured guardrail away from putting two tablespoons of nutmeg in your dinner.
...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.
Open source developers do not get paid already. I strongly agree developers need to get paid, but you’re not going to stop folks from producing open source for free.
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.
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.
> 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.
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.
> 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.
> 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.
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.
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.
So what you're saying is somebody took something that was public or at least community-owned and built a fence around it? Or, you might say, an enclosure [1]? Interesting. One could even describe this as rent-seeking behavior [2]?
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.
That's one way to look at it, another way to look at it would be something like a community farm where someone took a few ingredients that were just sitting there and being given away for free and cooked them up into something special and sold it.
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.
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 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
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.
...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.
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.
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.
I had repeated PRs for entirely hallucinated problems.
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.
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
We need the equivalent of that for open source software maintained by people from before 2004.
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.
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’
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.
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.
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.
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.
I believe that train has sailed on this association.
The fact that free software is benefitting at all from more coding power is a win. We have bottlenecks to solve though.
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.
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.
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.
...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.
https://rainshare.dev/ enables using up your token subscription to help others with their backlog, for example. Code forge goes brrr.
You cannot eat tokens.
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.
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.
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!
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.
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.
Rhetoric question of course, especially in the AI coding age.
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.
[1]: https://en.wikipedia.org/wiki/Inclosure_act
[2]: https://en.wikipedia.org/wiki/Rent-seeking
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.
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
Even worse, most of open source is now majority slop and it is highly likely that they will be abandoned.