Live data from Hacker News

Is It Even Worth Working on FOSS Anymore?

gavinhoward.com

11–20 of 284 posts

Re: Is It Even Worth Working on FOSS Anymore?

#11
Although I agree with many of the sources of frustration mentioned in the article, there is a way:

For most software projects, there should be a way to buy a commercial support license.

For many, such a license should be required for use in any org which is over X employees. Even if not enforced, this way a conscientious dev can justify for paying for the license.

In addition, for some of the deeper "plumbing" projects, that cannot be really charged for independently, they can included in the licensing of some of the projects that use them, as a clause for certain types of orgs, etc.

Something like - using X also requires a license for log4j of $50/yr - where that could even be a pittance, but included in many projects that benefit.

This will make the software much more reliable, while actually giving a basis for open source devs to have the funds to support themselves, feel self worth, and pay for a lawyer to protect their IP for things like TikTok's move.

As an open source coder, I theoretically love the above, but don't know what license, how to set it up, or how to handle the contracting and payment. In addition, I don't know how to justify my commitment - what exactly am I promising and how.

Nonetheless, if someone like Gitlab were to deal with figuring out the technical steps of the licensing and payments, you bet that I would be happy to move my code off GitHub for it (well, my code is already off GitHub, but whatever), and I bet many others would follow suit.

Re: Is It Even Worth Working on FOSS Anymore?

#12
post #5

Define "worth". We were never in it for the money. I maintained Dia for 8 years and never saw a penny. If you don't like your FOSS project being used by evil capitalist megacorps, put an anti-commercial license on it.

There's a licencing 'race to the bottom'. If there is a liberally-licensed alternative, resources will divert to that.

Re: Is It Even Worth Working on FOSS Anymore?

#13
post #4

The reasons you write open-source code: - training purposes to better yourself - as a showcase or to build up your reputation to get hired - because you have a niche need in your personal life that no one else already solved None of those reasons are invalidated by big corporations using open-source without paying back.

That does not work.

After several years of hard work a prior open source project that grew to immense popularity got me employment a few times. It wasn’t the actual project, code, or capabilities that meant anything. The only thing appealing about that project was it’s popularity.

Nobody ever looked at the code, except people interested in submitting pull requests. If you think a prospective employer will take the time to analyze the code you are either applying for an exceptional specialized position or completely mistaken.

Work on open source because you like to solve tough problems, want to grow as a developer, or because you just want to build some interesting product. Don’t kid yourself into thinking the code will immediately solve some business interest.

Re: Is It Even Worth Working on FOSS Anymore?

#14
post #3

It's always been this way. You shouldn't enter open source expecting accolades or deference. It's awful the way log4j is being treated. I just don't think anything has changed.

> It's awful the way log4j is being treated.

Sadly, that's the way all FLOSS gets treated. I saw this exact same sentence when heartbleed came out with just the project name changed.

I don't think that anti-commercialisation clauses in the license will fix anything, though.

Re: Is It Even Worth Working on FOSS Anymore?

#15
Is it 'worth' working on? That's a function of what I deem worthwhile, which no one else can really answer for me. 'Anymore' implies that it used to be better, which may be true, but I'm inclined to think I may have changed even more than the ecosystem. My time was worth less in the past, so it may have been a valuable use of time (valuable as a term leading back to the first point) than currently. Is there still value in working on FOSS? Yes. Is it worth it to you, or me, or any certain person? Maybe. Is it changing, likely for the worse? I think so, and the examples in the article are concerning.

Re: Is It Even Worth Working on FOSS Anymore?

#16
Yes,

The most important thing of FOSS has always been about ensuring an alternative to closed source. This provides people with leverage in negotiation with the corporations and states in a way they simply would not have without it. Beyond this, It provides a pathway for a much quicker evolution of the products, something actually driven by the most driven users, instead of corporates approved. Writing this on firefox on linux I'd say its working and has done, and will keep doing great good.

Re: Is It Even Worth Working on FOSS Anymore?

#17
Software is eating the world and it's mostly through proprietary licensing models. But this doesn't mean that the fight is lost. In fact quite the opposite: it means that FLOSS is more needed than ever. Generally, when a new area opens for software, proprietary software usually has a massive head start, but once the area becomes more well understood, FLOSS products emerge, and often they steal the show of the proprietary competitors, at least in the long run.

In the areas FOSS was able to get a footing, it usually remained. Web browsers have been trending towards the open core model for example, same goes for compilers, most of which are FLOSS. On the server, the GNU/Linux platform is the most commonly used one. Same goes for embedded applications including Android.

Does this translate to end user freedoms? Sadly, in many instances it doesn't. But I think it's still worth fighting for freedom, even if the only reachable audience is other freedom loving enthusiasts instead of the broad majority of people.

Re: Is It Even Worth Working on FOSS Anymore?

#19

The FOSS that was imagined by Stallman, where end-users could actually use FOSS products in their everyday lives, is not possible under capitalism. So what you have instead is effectively a network of semi-public property primarily for industry use. But, just as anything else that industry cannot turn for a profit, FOSS is and will always be in the lowest of priorities, if a priority at all. Cheers to Stallman, but a…

> The FOSS that was imagined by Stallman, where end-users could actually use FOSS products in their everyday lives, is not possible under capitalism

I have to disagree. Use a Linux based operating system, self-host your internet services at home, use google free android, or do a subset of that.

Its all open source and works locally.

Re: Is It Even Worth Working on FOSS Anymore?

#20
> I have written licenses to make GitHub hesitate before using my code as input to Copilot

Microsoft has claimed that consuming code for Copilot is fair use, and therefore does not require permission from the copyright owner, so how would a license—an offer of permission under limited terms—impact that at all?

> But even if I solidify the licenses, what stops GitHub from ignoring them by claiming that their Terms of Service allows them to use my code?

Well, the fact that arguing the ToS would be a retreat from their position that they don't need permission in the first place, whether or not the code is hosted on GitHub.

Post reply on HN