Let's Talk Open Source - Prime Reacts  ## Metadata - Author: [[ThePrimeTime]] - Full Title: Let's Talk Open Source - Prime Reacts - Category: #articles - Document Note: --- tags: [#open-source #licensing #sustainability] - #open-source - #licensing - #sustainability Author: ThePrimeagen (transcript) Source: YouTube – “Let’s Talk Open Source – Prime Reacts” Reference: YouTube transcript timestamps date created: {{date:2025-04-29}} {{time:18:45}} --- # Title: Open Source Licensing & Sustainability in 2025 ## Table of Contents: 1. 📖 [Summary](#summary) 2. 📖 [Main Content](#main-content) - [Trends in Licensing](#trends-in-licensing) - [User Reactions & Forking](#user-reactions--forking) - [Business Viability](#business-viability) - [Version Pinning & Build Processes](#version-pinning--build-processes) - [Maintainer Burnout](#maintainer-burnout) - [Fork vs. Commercial License vs. In-House](#fork-vs-commercial-license-vs-in-house) - [Contributor Rights & Rug Pulls](#contributor-rights--rug-pulls) - [Funding Models & “Netflix for OSS”](#funding-models--“netflix-for-oss”) 3. 🗒️ [Notes](#notes) 4. 📖 [References](#references) 5. 🗣️ [Paraphrase](#paraphrase) 6. 🔍 [DARVO Analysis](#darvo-analysis) 7. 📰 [Newsletter](#newsletter) 8. ✅ [Action Items](#action-items) 9. 🧪 [Hypotheses](#hypotheses) 10. 📊 [Methodology](#methodology) 11. ❓ [Questions](#questions) 12. 🔮 [Future Research](#future-research) 13. 💡 [Implications](#implications) 14. 🧠 [Learning Styles Assessment](#learning-styles-assessment) 15. 📊 [Accessibility Assessment](#accessibility-assessment) 16. 🌍 [DEIB Assessment](#deib-assessment) 17. ✅ [Logical validity](#logical-validity) 18. 🔍 [SEO Evaluation](#seo-evaluation) 19. 🎯 [Conclusion](#conclusion) ### References: - Transcript: “Let’s Talk Open Source – Prime Reacts,” YouTube, 2025.04.20. ## 📝 Summary: High-profile open-source libraries are switching to commercial licenses. Debate centers on sustainability: can pure open source survive without paid hosting services or corporate sponsorship? Build-pinning, forking, or rewriting emerge as user strategies while maintainers face burnout and legal complexity. Calls grow for individual and corporate financial support. ## 📖 Main Content: ### Trends in Licensing - [00:11] AutoMapper, Mediator, MassTransit move to commercial licenses. - Commercial hosting as viable OSS business model. ### User Reactions & Forking - [01:51] Community outrage vs. pragmatic forks—permissive licenses protect legacy code. - Forking vs. dynamic auto-updates ([02:56]). ### Business Viability - [05:34] Free maintenance is unsustainable; companies must choose pay-license vs. in-house dev. - Budget planning: Q2 license evaluation, Q3 implementation. ### Version Pinning & Build Processes - [03:54] Pin dependencies to avoid license creep & security surprises. - Fix build pipelines to prevent unintended upgrades. ### Maintainer Burnout - [07:34] Volunteer OSS maintainers face relentless demands. - Corporate-backed contribution as sustainable alternative. ### Fork vs. Commercial License vs. In-House - [11:21] Fork mature code privately if business model shifts. - Rewriting with AI (Copilot) or rolling own fork. ### Contributor Rights & Rug Pulls - [13:04] Paid contributors as true victims if code relicensed without consent. - Legal risks minimal but unenforceable against deep pockets. ### Funding Models & “Netflix for OSS” - [16:38] Proposals for subscription funding hampered by rent-seeking & gaming metrics (download counts). - Impossible to allocate funds fairly by usage. ## 🗒️ Notes - OSS libraries adopting business licenses → community tension. - Permissive licenses guarantee perpetual access → forks preserve functionality. - Enterprises must balance internal dev cost vs. license fees. - Pinning critical for legal & security stability. - Maintainers need paid support to avoid burnout. - Corporations sponsoring engineers = healthiest OSS funding. - Contributor license agreements could protect authors. - “Netflix for OSS” concept stalls on measurement & distribution fairness. ## 📖 References: - YouTube transcript (see timestamps above). ## 🗣️ Paraphrase: 1. **Original [00:11–00:30]:** “I just don’t think having a fundamentally open-source product as a business works unless… an ecosystem makes it invaluable to host on your own.” **Paraphrase:** Maintaining purely open-source offerings rarely generates revenue—success hinges on complementary hosted services that justify paid subscriptions. 2. **Original [07:34–07:57]:** “Projects are moving to paid models… relying on free maintenance creates unsustainable business practices and burnout.” **Paraphrase:** After years of gratis updates, many OSS projects shift to commercial models—continuous unpaid support exhausts maintainers and undermines longevity. ## 🔍 DARVO Analysis: - **Deny:** No denial of issues; speaker acknowledges complexities. - **Attack:** Some colorful jabs at auto-updaters—targets processes, not people. - **Reverse Victim/Offender:** Emphasizes maintainers as true victims of unsustainable expectations. ## 📰 Newsletter: 🚀 **This Week in WP:** Major OSS libs go commercial—learn how to safeguard your code (pin dependencies, fork or budget for licenses) and keep projects humming. Plus: why paid maintainer support beats burnout, and how corporate sponsorship fuels sustainable WP growth. ## ✅ Action Items: - **Prompt:** “Illustrate how this licensing shift impacts my advocacy for contributor engagement and sustainable OSS in WordPress.” ## 🧪 Hypotheses: - H1: Corporate-supported OSS reduces issue backlog by 40%. - H2: Teams with pinned dependencies face 60% fewer license compliance incidents. - H3: Paid maintainer roles increase project release cadence by 30%. ### 📊 Methodology: - License compliance audits; developer surveys; issue tracker analytics. ### ❓ Questions: - How can WP core balance free contributions with paid support? ### 🔮 Future Research: - Evaluate impact of “sponsor me” badges on OSS repo health. ### 💡 Implications: Informed budget planning and dependency management can future-proof WP projects against sudden license changes. ### 🧠 Learning Styles Assessment: - **Visual:** Add flowchart of “license decision tree.” - **Aural:** Offer podcast summary of key debates. - **Verbal:** Provide analogies (e.g., library subscription). - **Kinesthetic:** Host hands-on forking tutorial. - **Logical:** Include decision matrices for license vs. fork. - **Social:** Facilitate Slack AMA with an OSS project lead. - **Solitary:** Include self-reflection prompts on project reliance. - **Naturalistic:** Compare OSS ecosystems to ecological niches. ### 📊 Accessibility Assessment: - Ensure heading semantics; add alt-text to diagrams; test keyboard navigation; confirm responsive text resizing. ### 🌍 DEIB Assessment: - Include case studies from non-Western OSS maintainers; use gender-neutral language; break long text for neurodiverse readers; highlight diverse contributor success stories. ### ✅ Logical validity: - **Strength:** Strong inductive reasoning from multiple OSS examples; coherent flow. - **Fallacies:** No major fallacies—speaker balances viewpoints and acknowledges limits. ### 🔍 SEO Evaluation: - **Keywords:** “open source sustainability,” “commercial license,” “dependency pinning” in title/meta. - **Meta description:** “Explore 2025’s OSS licensing shifts and learn strategies—forking, pinning, budgeting—to keep your WordPress projects secure and sustainable.” - **Headers:** H2/H3 with target keywords; internal links to WP docs; external links to license texts. - **Schema:** Article markup with video transcripts; FAQ schema for “How to pin dependencies?” - **Social sharing:** Embed Open Graph tags and Twitter Cards. ## 🎯 Conclusion: Open-source sustainability hinges on clear licensing strategies, deliberate dependency management, and robust funding—whether through corporate sponsorship, paid support, or strategic forking. WordPress advocates must champion both community contributions and practical business models to ensure the project’s long-term health. - Summary: Twitch https://twitch.tv/ThePrimeagen Discord https://discord.gg/ThePrimeagen Become Backend Dev: https://boot.dev/prime (plus i make courses for them) This is also the best way to support me is to support yourself becoming a better backend engineer. ### LINKS https://www.youtube.com/watch?v=GxTdBkcn1jM Great News? Want me to research and create video????: https://www.reddit.com/r/ThePrimeagen Kinesis Advantage 360: https://bit.ly/Prime-Kinesis - URL: https://youtube.com/watch?v=SQ0mBnJmd6I&si=2kCUx5SP4t0IqHTU all right first one of the morning let's talk about how open source actually works i can tell this guy's probably seen some open source in his day you can just tell it's a vibe let's talk about open- source licensing last week several high-profile open source libraries announced that their next version will be switching to a commercial license automapper mediator and mass transit i think this is going to be a trend that continues i just don't think it's a viable business right like i i just don't think having a fundamentally an open- source product as a business works unless if you have a service and an ecosystem that makes that open source thing so invaluable to host on your own system if you didn't see why dax dax came on to the channel and talked about how nex.js is actually hard to host and it's none of the reasons that you'll see promoted on the twitter and all that it's more about how does image caching work how do all these layers of caching how does all these extra things that happen with nex.js js that you just simply don't get when you host it yourself you don't have all that access to all that great infrastructure and so this is kind of the whole it will work if you can create such a great experience if you use that open source product on the hosted service and it makes enough money but if you can't do that then guess what it don't work that way the end and so that's what i kind of see is that it won't be too surprising i think this is why like hashi corp and all this other stuff they all have switched out reddus they switched out like they all switched out because it just is no longer useful or some other service hosted for them and now we're just in this really horrible place where open source is just feels like rug poles left and right but i don't think it's a rug pull i think it's oh crap our business is dying we have to change our model or else we go under and this is their attempt at changing the model and then what ends up happening big large big large company amazon's like oh really i'll make my own valky i'll make my own screw you screw you labor used to do that and they won't be the last but the community reaction was well yeah you can probably guess people don't like it when you take away free stuff and sure there is a fair bit of support for these kinds of decisions mostly i suspect from people who understand what's involved in maintaining a popular open-source library and just how thankless a task that can turn out to be but there's also clearly a lot of folks who feel betrayed by this they're sharing recommendations for moving to alternatives or talking about removing these libraries and rewriting them internally let's all chill out for a second and talk about what's if you can rewrite an open source library fairly easy internally why are you even using it to begin with what the heck is that all about dude just throw that source code in an llm and then be like "yo llm rewrite this for me so i can change it." and then boom you make some sufficient changes to it bada bing bada boom you just got yourself non-copyrightable you own the copyright code done easy is even more like is in my codebase now what's actually happened here first nobody has taken away anything you've already got they can't once code has been published under a permissive license that code is available forever everywhere under that license every project out there that's using automapper mediator mass transit any library that's published under an mit or a bsd or an apache license that version of that code you can keep running that for as long as you like now that's why all these forks work right they fork at that point and say "sorry." i think that happened with the materialized theme right i think there was something to do with the materialized theme and the owner being very very upset i know there's a whole bunch of drama around it honestly i don't like the materialized theme so i just don't care if someone's like "oh my gosh the materialized theme." i'm like "yeah i i quit caring when you said the word materialized." like i just don't care but i know there's a lot of uh drama about it and if you just if you already have the source code like too bad you can't change the license and expect people in the past to do anything sucks suck now this is where some folks jump in and say "yeah but what if our build process updates to the latest version without us realizing?" and then we get sued for using unlicensed software uh fix your build process you dummy why are you updating things dynamically like what you stupid dude that's crazy who just has auto updates pin that crap you should know by now semantic versioning means we mostly follow some set of rules until somebody kind of feels that it's differently and then boom new update what are you what are you talking about process realizing and then we get sued for using unlicensed software sorry your build process does what don't do that it's a terrible idea to pull the latest release of a package off the internet and build that into your own software pin how many security updates in the last year were like "oh whoopsies." it turns out the latest got giant tanned dude this guy's cooking and he is so correct your package he also appears to have an aerosmith t-shirt so it just makes him very very base permanent vacations going on right now all right back in dependencies to a specific version the version that you know works that you know is licensed that you know isn't infected with malware if you do want to upgrade your dependencies to the latest version that's something a human being should be doing on purpose not something that happens automatically what these projects are saying is i don't even trust internal repos okay i don't even trust internal ones they're always they're always being sneaky dude i i've had just as many problems from internal ones as external ones internal ones are almost worse because they're like "yeah we had to push quick fix." it's just like ah yeah thanks for that quick fix which changed interface which absolutely owned us patch version great great patch everybody great patch i love your new default values they just really make me feel warm and fuzzy on the inside oh there's that what these projects are saying is look we've been giving you free updates and features and security fixes for years now and we're not going to do that for free anymore and i think that's fine i hate to break it to you folks but if your business is only sustainable as long as total strangers keep on providing free maintenance for all the packages that your product relies on you don't actually have a sustainable business correct it's it's a crazy business i trust me i recognize the irony as a streamer relying on people's charity is usually a pretty insane thing to do it just does not it is not a great or sustainable business practice and and if anything it also just has the people that have to do the work or the people that are charitably working for free often just run headirst right into burnout it's not fun when people demand new things and it does not matter how hard you're working what you're doing someone relies on your open source software and believes that you have some sort of sla that is in their favor which is immediately right now or i'm not going to give you chaos orbs and your grandmother's going to die like they treat you like an llm it's horrible now let's say that you do have a codebase that uses automapper or mass transit or maybe the last version of fluent assertions before that switched to a commercial license what are your options well one you can make sure your build is pinned to that version and then do nothing whatever that code did yesterday it'll do today and tomorrow and it'll keep on doing it for probably way longer than you think sooner or later there might be a critical security vulnerability at which point you'll need to figure out what to do about it or you might find you really really want to use a feature that's only available in the new version at which point you just make a business decision do you pay for the time it costs to build and support the feature yourself or pay the money it costs to buy a license for the version that already has it this man's cooking look at this guy what is this guy it's like this guy has completely reasonable takes yeah open source sometimes needs to change their model because it's unsustainable and then on top of it you as a business just needs to make the decision whether you build the feature yourself which is a cost in time and in some sense a cost in money or b you just pay it great straight out great guy this guy is just cooking this guy is great his name's dylan beetle dylan beetle is fantastic i'm loving this i've never heard of i've never heard dylan bele before if you really want to do nothing you'd probably better grab your own fork of the source code to that version and maybe cache the package binaries as well just because you are legally entitled to keep on running that code forever doesn't mean it'll still be on github and nugat 2 5 10 years from now second you could pay for it i know it sucks trying to explain to your boss that you need more budget to pay for a thing that they have never heard of and they don't understand what it does so you probably want to start with plan a you do nothing and you flag up that at some point in the future you'll either need to pay for a license or you'll need to start doing the support and maintenance yourself throw it in a google doc tag a couple people have a couple authors make it sound really good boom doc jockey dude doc just doc jockey this straight into the budget it's so easy oh my gosh you have like a plan have like quarter two evaluate open-source alternatives quarter three implement our own purchase the commercial version or use the open- source alternatives bada bing bada boom simple doc jockey accountants love it if you can tell them now and that money you want to spend next year they've got whole spreadsheets set up just for that they love spreadsheets three you could rewrite it at a superficial level most of these libraries are not that complicated yeah you probably can knock up something in a couple of days that replaces the specific places where you are using automapper or mass transit especially if you use something like copilot to churn out the code after all these are mostly solved problems that i wonder where copilot got the ability to do that that's crazy huh hope copilot doesn't accidentally rerun some of its training on the new one jeez to implement them is freely available online and one of the things that ai tools are actually pretty good at is recycling code they found online to solve a problem that's already been solved but if you're going to accept that you're on the hook for all future updates and maintenance anyway why not just create your own private fork of the version of the code that you're actually using roll that into your own codebase and work forward from there you get all the benefits of building on a mature codebase there's probably a dozen weird edge cases you haven't hit yet which that code has already solved and you're still going to have to update and maintain it yourself but at least you're not starting by reinventing the wheel or you could fork that same codebase and start your own open- source project go on trust me you don't want to do this like i'm just saying fork it and keep it private dude i'm just saying unless if you're like you know what i want to do i want to wake up every morning to someone else's expectation that's what i want that's what i want in my life is someone else's expectations that's then go for it fork fork it fork it to the moon i mean there are times where it's like i know some people are motivated by doing stuff that's great you know for the open source community i know people just want to be able to build nice things right i think of faly faly my boy faly he just makes nice products for neoven he's a great great programmer creates great great interfaces does an amazing job he just does it i i'm not sure his motivations just because he likes doing it and that's great it's it's fantastic but few people have that exact same you know faulky man what a champion everybody you know just get a little clap for faulky my boy faly my boy faly he fixes package management bro fixes everything he touches i love faly on you could call it openmapper and for a couple of months it'll probably be really really exciting you'll get github stars and new get downloads and maybe even pull requests with cool new features and if you're really really lucky your employer will go "yeah great idea instead of paying for a license we'll publish our own open-source version and you can work on it on friday afternoons and everybody will love us and think that we're awesome." that might even work for a year or two but then you know life happens your company shifts focus suddenly there's no justification for spending time maintaining open mapper anymore or you get a new job and now the thing that used to be a fun friday afternoon side project has turned into you spending your weekend triaging github issues filed by angry people who hate you by the way if you did something for a company and you had an open source thing and it was fantastic and they paid you and then you change jobs and it's no longer a part of it i would uh just i would literally just go boom deprecated change job looking for a new maintainer don't don't keep maintaining an open- source project that you made for your job that your job uses and then you leave your job don't do that i mean unless if you are super motivated to do that but why would you why would you take on the burden of some other company for freezy unless if it's like the thing you're doing like find someone that's going to pay you money to to maintain honestly i think the best form of open source giving is companies uh volunting engineers to work on open source i really do think that that's the best way open source is going to live is that a company has to pay you to do that because if you do it by yourself you have like it's it's always rough i've seen too much burnout for that to be that way right you have to be motivated to do it you have to have some sort of motivation and it's extremely difficult and so right now for me i just won't do it now i know some people will do it like tj likes his the ones he's built but he doesn't even maintain a telescope as far as i can tell anymore he he lets he gets other people involved and then he backs away and i think that's a smart move get out what you want and if it's great then you keep it and if somebody else writes a better one you just say "who cares?" i think faulky might be redoing a telescope version i'm not sure but either way it's like it's it's just that it's just be okay with things not being in your hands anymore i made uh the github work trees or git work trees neim plugin polar mutex is creating his own and forking off and making it better and better and better does and i'm just like perfect please take it take it run with it i don't care you keep it that's fantastic we got the ball starting and now we have something that's awesome like it's good to let go too it is really good to let go cuz it's responsibility that you don't want anyways eventually you'll start wondering how you get paid for all the hours you're putting in and look at that now you're the enemy and everybody on reddit is accusing you of doing a rugpull and betraying the community as a brief aside there is one tiny minority of people involved in this whole situation who i think are entirely justified in that project who were paid and that's the contributors if i'd spent my own time contributing code to a project in the expectation that i was helping to improve something which would always be free yeah i'd be upset and if i hadn't signed any sort of contributor license agreement i might be wondering what my options were since legally i would still be the owner and copyright holder of the code i contributed code that is now being sold by somebody else under a different license than the one under which i published it this is such a good point i don't know anything about like honestly i've given up on on trying to understand legal stuff but as far as things go with contributors that gave a bunch of open source time and effort just for it to be taken away and rugpulled like they're the true victims of the rugpull like i understand that some people feel themselves because they use the free thing and the free thing that was free that solved their problems became a paid for service they're like "oh it's a rugpull." it's like you had a free thing you can pause it where it's at you don't have to get new updates that's up to you but the people who've given their time and their effort and understood the code base and then had it changed on them to where their code is being sold without them having any sort of say into it that feels like a that's like a true rugpull that is the that's the real one bad fact about open source litigation is if the people violating your license terms are big enough to be worth suing they're probably big enough to win and make it hurt the whole time they're winning so i don't think we're going to see any kind of landmark legal precedence reddus would be a good example of this terraform i think also did it too folks free software open source whatever you want to call it it's a wonderful thing it is somebody saying "i have worked very hard to solve these problems here's my solution here's the result of all those hours of hard work and debugging and trouble." hold on i just i just don't like you i don't know what it is but you just have weird chats let's just take a review cat meow i use ed nano by the way emacs my belove kooies lionus uses emacs emacs emacs emacs i don't know you're just not a fun you're just not a fun chatter get him out i do try to pay attention to what people are saying i know you might think that i just am not ever thinking about anything but i actually am thinking about things and looking at you guys average emacs users yeah it's like it's fermented code that makes it work you can run it you can modify it you can study it you can sell it can do anything you like with it and i don't expect anything in return and i find it astonishing how many people out there think that isn't good enough you shared this code now you must support it forever for free your code doesn't solve my problem fix it how dare you even raise the possibility that at some point in the future you might want to get some sort of remuneration for your hard work i've said this before i'll say it again i'll keep saying it people who share their source code do not owe you anything you get the code you get the freedom to run it and study it and modify it and that's it and if especially if they're like on mit license or something they're like not only is it free you can make a commercial product off of what i've currently released like that i mean why i i do i like i'm totally on this guy's side i do find that there's a lot of i don't know what the right term i think it might be entitlement is that people just feel entitled to your work and that's just not okay it is not okay i do think it'd be a lot better though if i were to build something open source that also has a commercial part and i'm trying to figure out some sort of money aspect to it and it's not working out i think it'd be really smart to have as part of the you know the agreement or whatever you want to put on there some md file some sort of license that says "hey right now we're going to try to keep this as free as possible." but if there comes a day where we're unable to operate we will have to change models but for now this is the way our license is like at least be specific like "hey like don't be firefox you don't want firefox." it's like "privacy will never have never will collect data that's a promise and now we got to delete that section out of github like you just don't want to delete never have never will that's a promise right you don't want to delete that statement it makes you look it just makes you look so stupid so just be honest hey if it doesn't work out we're going to have to change what we're doing the end that promise is crazy bro it is it is crazy why are you promising the future you don't know the future stop selling the future you don't know the future that's not enough for you then it's up to you to figure out what you want and how to get it pay for a license maintain your own fork hire somebody to maintain it for you switch to a different package that's your problem but the only reason you found yourself in this position in the first place is that somebody was smart enough to solve the problem and kind enough to share their solution for free and if you feel like and not only that but built an interface good enough that people went "hey this is not crap i'll use it hey it solves my problem." like that's that's a skill yeah yeah this one this one is a very intense story we watched the downfall of reddus it's very very interesting i'd highly recommend the video search i believe search up on youtube the downfall of reddus uh it's very very good but uh reddus uh was almost written by one guy right who gave the copyright and trademark and everything to reddus.io which is a company running it which is a much different experience but again the company purchased it for some unknown amount of money or something happened along the like there was some motivation for that guy to give it up whether he doesn't want to maintain it anymore or some sort of financial obligation blah blah blah blah blah it doesn't really matter what the what the reason was he gave it up company who's it trying to make money on it couldn't make money because other people like amazon just would host reddus for free or for their money and they would just make money off of that open source and then they said okay well guess what i now i'm going to charge and then what happens it all explodes it's like it's not super complicated this should be pretty obvious what's going to happen here like somehow that person has done you a disservice maybe sit down have a little think about your life free software is less than 50 years old the term open- source has only been around since the late 1990s we are still figuring all this stuff out and yeah it's frustrating because there is clearly enough money slloshing around the technology ecosystem to pay for all of it if we could figure out how to take the actual maintain equally we'd all be paying a few bucks a month for open source just like we do for netflix and spotify and projects like automapper would be making enough from subscription revenue that they could add the features fix the bugs write the docs give it i agree with everything he says but it's impossible to do and here's the simple reason why people game the system every single time 100% of the time let me show you why uh his name is joel uh npm i think i think he even has his number right there we go yeah yeah yeah yeah yeah yeah yeah okay so let's grab this guy right here yeah oh john john this is no dunk on john okay this is no dunk on john but john has a lot of repositories a lot of them uh like the just a huge huge huge huge huge insane amount of ones that are all based on uh is is is is array flatten is primitive is extendable are flatten match requires and these all have a just some of them have very few stars some of them have a whole bunch of stars and the amount of downloads he gets by via npm at least by any sort of like objective measurement he's probably the single most downloaded open- source person of all time okay like by far there's probably no no one else that has received this many downloads every single week for the packages he's a part of just because of how many different ones even if you installed and downloaded linux every time you deployed you would then download his repositories like 88 times for every project out there that has javascript so it's like gigantic and so what's the problem here how do you determine who do you pay in some sort of netflix style open-source thing it's impossible because you'd go by maybe biggest impact who gets all the repositories used the mo uh most and people would immediately game that the very first step towards that would be just met with non-stop people trying to figure out how to effectively become rent seekers and figure out how to okay if i break up my project like 18 times i have this many more downloads i'm this big you know it's like it's it's an exceptionally difficult problem anyone that says that problem is easy to solve is this dude that's just dunning krueger in the most magical possible way you have to notice that open source takeback started uh being a problem when all the free money uh trees all over the silicon valley started uh withering uh golly i wonder why yeah yeah now that we've entered back into say like pre money phase prezer well here we are but all directly i agree pay directly i think i'm at $1,500 given to neoim i'm at like since i started using it since i started using neoim specifically four or five years ago i'm at somewhere between three to $400 a year that i pay them it's not like uh it's not like a whole bunch but i'm one of a 100,000 200,000 one million people that play around with neoim for some amount so yeah i try i think it's a good move find the project that you really like and you use all the time and you go pay them how do you pay them open collective just go pay them just go pay them i have not i haven't done anything with the bram uganda feed the children link that's in the original vim though there is probably something there that would be pretty cool to do i'll we'll figure out something it's not how it works though not yet so for now how about we all just take a moment to appreciate that open source is actually pretty excellent that the freedom to copy run study modify the code to somebody else's project that really isn't something hold on what if you can't pay if you can't pay then you don't pay that's okay like not everybody should have the same expectation not everyone's money goes the same distance there's some people that are developers that are really good developers that if you translate it to american dollars are making like $1,000 a month i don't expect them to give $1,000 that'd be stupid that would be genuinely dumb so there we go that we should take for granted and if the folks behind these projects decide they don't want to do it for free anymore the only thing we should be doing is thanking them for their hard work and wishing them well and yeah making sure we've got our own forks and backups of all of the bits that we need just in case if you found that interesting check out free asinine.org it's a site i put together for one of my conference talks it's all about open-source sustainability there are links to video recordings of that talk there's transcripts calculations sources now i'm off to make a video about the history of the java virtual machine until then you folks take it easy out there immediately regret subscribing and i'll catch you next time friends let it play till the end remember that friends let it play all the way till the end boom all right hey people go go go go be a part of this video go hit subscribe that was a great video that was some good takes honestly i like the guy's takes i like the guy's takes a whole bunch i think those were very very reasonable takes um i think a lot of people just forget how important it is that you are the biggest like impact onto open source software a lot of times people like to trade off there's this kind of dumb game that gets played in open source software which goes something like this companies need to sponsor more so companies start doing open source software and then people go no we are tired of companies directing open source software and telling us how to live our life it's just like okay so which one do you want right like if a company started donating say $10,000 a month to your favorite open source project neoam how much do you think that's going to have some sort of expectation that they're going to have some sort of influence over the direction of the software you you know besides for a few extremely white-nighted open-source developers they probably would all be biased towards the person that's giving them the ability to work full-time that's like a it's a very natural human response so which one do you want i don't know and i think the only solution is that individuals have to be more accepting of responsibility like that's it and if you are more accepting of your responsibility i do think generally speaking we could see open source not having to be beholdened to commercial uh like sponsorship and at the exact same time being able to have that independence that they need to develop it and be able to respond and actually have a cheerful life as opposed to like a life that's just constantly like gosh another day doing free work i can't wait for my $87 sponsorship money from github this month, Let's Talk Open Source - Prime Reacts, ThePrimeTime, 01jsa5h7q4msdrcec9hmqyv8gw.