The Internet Relies on People Working for Free (medium.com) 89
Who should be responsible for maintaining and troubleshooting open-source projects? From a report: When you buy a product like Philips Hue's smart lights or an iPhone, you probably assume the people who wrote their code are being paid. While that's true for those who directly author a product's software, virtually every tech company also relies on thousands of bits of free code, made available through "open-source" projects on sites like GitHub and GitLab. Often these developers are happy to work for free. Writing open-source software allows them to sharpen their skills, gain perspectives from the community, or simply help the industry by making innovations available at no cost. According to Google, which maintains hundreds of open-source projects, open source "enables and encourages collaboration and the development of technology, solving real-world problems."
But when software used by millions of people is maintained by a community of people, or a single person, all on a volunteer basis, sometimes things can go horribly wrong. The catastrophic Heartbleed bug of 2014, which compromised the security of hundreds of millions of sites, was caused by a problem in an open-source library called OpenSSL, which relied on a single full-time developer not making a mistake as they updated and changed that code, used by millions. Other times, developers grow bored and abandon their projects, which can be breached while they aren't paying attention. It's hard to demand that programmers who are working for free troubleshoot problems or continue to maintain software that they've lost interest in for whatever reason -- though some companies certainly try. Not adequately maintaining these projects, on the other hand, makes the entire tech ecosystem weaker. So some open-source programmers are asking companies to pay, not for their code, but for their support services. Daniel Stenberg is one of those programmers. He created cURL, one of the world's most popular open-source projects.
But when software used by millions of people is maintained by a community of people, or a single person, all on a volunteer basis, sometimes things can go horribly wrong. The catastrophic Heartbleed bug of 2014, which compromised the security of hundreds of millions of sites, was caused by a problem in an open-source library called OpenSSL, which relied on a single full-time developer not making a mistake as they updated and changed that code, used by millions. Other times, developers grow bored and abandon their projects, which can be breached while they aren't paying attention. It's hard to demand that programmers who are working for free troubleshoot problems or continue to maintain software that they've lost interest in for whatever reason -- though some companies certainly try. Not adequately maintaining these projects, on the other hand, makes the entire tech ecosystem weaker. So some open-source programmers are asking companies to pay, not for their code, but for their support services. Daniel Stenberg is one of those programmers. He created cURL, one of the world's most popular open-source projects.
Re: (Score:2)
Isn't that basically what RedHat and Canonical do?
Re: (Score:3)
Re: (Score:1)
Something missed is that people write open-source software for status (recognition, fame, esteem, etc.)
There are good evolutionary reasons we value status, sometimes over money.
Federal Judges are an example. They typically give up half or more of their income as a lawyer for the higher status of being a Federal Judge.
Argument for a Basic Income etc. (Score:2)
The issue here is not that programmers don't want to work on infrastructure or FOSS. Many do. The challenge is that they can't afford to do it in a society that emphasizes financial exchange transactions. So, a Basic Income would make it more feasible for more software developers to work on truly important things like high-quality FOSS infrastructure and also other FOSS software that supports other laudable goals which may not be so easy to monetize for whatever reason. This is a situation where other types
Re: (Score:2)
Not sure what you are talking about. A lot of programmers get paid to work on infrastructure and FOSS. Are you guys from 1992?
Re: (Score:2)
LOL. I'm talking about the subject of this article: that the internet relies on people working for free and that many of them get burned out doing that given at the same time they need to maintain paying jobs on different software. But that is also true in more areas of our culture than software infrastructure. There may be thousands of programmers getting paid to work on FOSS infrastructure at companies like RedHat and so on -- but that considering how billions of people now rely on that infrastructure (an
Re: (Score:2)
Re: (Score:2)
Where does the "free money" come from for roads, bridges, defense, libraries, social security, government research, and so on? One way is that a community decides that some appropriate level of taxation or other means of raising revenue (tariffs, fees, printing money, etc.) is worth the benefits to society.
Of course, to avoid money, one can also strengthen the subsistence economy (better 3d printers, better solar panels, better gardening robots) or strengthen the gift economy (more people giving other thing
Re: (Score:2)
Include various bugs, vulns, and confusing configuration options in your FOSS.
That's a tight rope to walk. Try to milk it to much, and you'll see your project forked.
1998 called, and they want their FUD back (Score:5, Funny)
Guy writing for free on a free blogging site says you shouldn't trust free software.
Re: (Score:2)
The disinformation trolls are everywhere these days. They choose a rubric (perhaps financed as you imply), then shake the tree.
Re: (Score:3)
1998 is apparently calling back again, and delivering "Microsoft thinks that Linux is evil" FUD.
Modern day Microsoft doesn't give a shit what OS you use, as long as it's hosted on Azure or using API calls to other Microsoft web services.
Re: (Score:2)
Yea. I'm sure they would gladly hand over their corporate lock-in for Exchange/Server/Office/Windows /s One thing is clear. Microsoft, like most other companies, only plays nice when they have to. There are many examples like I.E 6, doc-> ooxml, where they try really hard for vendor lock-in, eschewing standards and building in MS only features and formats. Then they "play nice" when they lose their grip. Internet Explorer is probably the latest example, coming full circle. Browser based apps and op
Re:1998 called, and they want their FUD back (Score:5, Informative)
Re: 1998 called, and they want their FUD back (Score:2)
Re: (Score:2)
No, you are paid $200 to write a blog on a crappy website. If you don't deliver clicks they will stop paying you $200.
Re: (Score:2)
So you counter the OP's statement that he gets paid by saying he gets paid? You're almost mentally retarded enough to run for president.
Re: (Score:2)
I didn't interpret his article as suggesting that you shouldn't trust free software.
It was drawing attention to the inherent conflicts in extensively using a resource for which there are no guarantees of continued maintenance and support, limited financial incentives to do so, and a level of contention regarding whether those financial incentives should even exist.
Seemed reasonable to me.
Re:Misleading Framing... (Score:5, Interesting)
Most people I know will design some new software from scratch for free, and will get it to the point where it does everything they want it to do. Then leave it alone and move on to NEXT BIG THING.
Support usually costs money. People don't like to maintain stuff for free, it's boring, requires fitting in to someone else's schedule and you won't get any of the credit, even if its your work alone that's making the pile of code useful to anyone else at all. Even if you are basically redesigning that thing in pieces, because it has a lot of problems.
Corporations are usually well suited to the pay for support model. They're actually not good at having things designed from scratch, for a lot of reasons. The difficulty is finding someone to support said pile of code who isn't in the company (because the company doesn't "own" it, they are reluctant to pay an employee to do it, even if it means paying a freelancer MORE, because...capitalism? Who knows.)
Re: (Score:2)
The difficulty is finding someone to support said pile of code who isn't in the company (because the company doesn't "own" it, they are reluctant to pay an employee to do it, even if it means paying a freelancer MORE, because...capitalism? Who knows.)
Probably because a freelancer has more incentive to keep the software generic and useful to other people and build a community around it to attract more gigs. I expect that if you put an employee to maintain it with no skin in the game outside the company it'll pretty soon go from an open source project to effectively custom internal code. It's so easy to take shortcuts that works for you but is mangling functionality you don't use or is relying on assumptions that won't be true for everyone else or has dep
Re: Misleading Framing... (Score:2)
Working for free is much better. Nothing stopping you from writing the code you want. Working for someone, you're pretty much always forced to make trade-offs in quality or design. Most people getting paid to code don't even control which projects they work on, much less how they go about it.
Re: Misleading Framing... (Score:2)
Re: (Score:3)
If I put an old appliance out at the road and hang a "Free" sign on it, and you pick it up, you don't owe me anything. Even if you value it, you don't owe me anything.
Re: (Score:2)
Re: (Score:2)
Hey, if you use it, and make money from it, that means you value it. So, whether I started for free or not, you owe me now.
I like that. My reply here, you have read it, and that means you value it. So, whether I started for free or not, you owe me now!
Re: (Score:1)
Re: (Score:2)
Now, ethically, I SHOULD share some of me income from your code with you, but legally, I owe you NOT ONE THIN DIME.
Re: (Score:1)
facepalm (Score:5, Insightful)
We get it . . . open source devs are the new victims, voluntarily exploited just like Uber and Lyft drivers. Quick, blame the nameless global multinationals on the Twitter! Outrage! Outrage!
Seriously, how does this shit even make Slashdot?
Re: (Score:2)
Seems like you're really overreacting to someone mentioning a possible issue.
Re: facepalm (Score:2)
What's the issue? This is how shit has been since the 70s, at least. There was a weird 80s/90s era blip from MS that made it appear for a moment like it might turn into something more formalized and professional, but it never happened.
Facepalm On The Other Hand (Score:2)
Re: (Score:2)
Re: Facepalm On The Other Hand (Score:2)
If you are a coder who has avoided learning the basics of copyright law, there's no help for you.
Re: (Score:2)
People who write the clever code that ALLOWS THEIR PRODUCTS TO EXIST have no claim to any sort of compensation???
(I know your post is tongue in cheek, but it deserves a serious response for anyone who might take it seriously.)
The truth is that most open source developers today do get paid. There's plenty of free work being donated to a multitude of tiny projects, most of them used only by their authors, but all of the big projects are developed primarily by people who are paid for their work. To take the most prominent example, look at the the stats [lwn.net] for a recent Linux kernel release. Only 3.9% of lines were writt
Re: (Score:2)
Seems even simpler than all that.
I take offence at these people for denying me my right to choose $0 as my price.
They kind of are in a lot of ways (Score:3)
Worse, I've had friends that have had "Job Interviews" where they're called in to solve a problem as a "test" and it's very clearly the employer trying to get free consulting services. A few of them wrote the code for free without getting a job when they were young and dumb and didn't know better. I gather since India took ov
Re: They kind of are in a lot of ways (Score:2)
My GitHub account is mostly shit I got paid to write. Not sure why you think people aren't getting paid for that stuff.
Now, if your GitHub account is filled with half projects including a bunch of framework boilerplate that doesn't do anything useful, you probably should not get paid for that. But that's exactly what the "portfolios" you're talking about are.
Re:They kind of are in a lot of ways (Score:5, Informative)
Worse, I've had friends that have had "Job Interviews" where they're called in to solve a problem as a "test" and it's very clearly the employer trying to get free consulting services.
I don't believe your friends. I'm not saying they're lying, just wrong.
Any problem that could be solved in the course of a job interview is too trivial to be worth paying for, and any company that would use such code is completely stupid. If they are so completely lacking in engineering talent, what are they going to do if the code breaks, or doesn't work exactly the way they want?
What I believe is common is for interviewers to ask for solutions to real problems that they have faced in their work. There are several advantages to using such real problems, rather than the typical contrived ones, among them that the interviewer has spent weeks, or months, thinking about the problem and potential solutions, and is therefore well-positioned to evaluate the advantages and disadvantages of the candidate's solution -- recognizing that the candidate had very little time. The biggest disadvantage is that real problems are often too complex to even explain in the course of an interview, much less have time for the candidate to generate and code a solution. Often they can be suitably simplified without losing their connection to reality, though.
It wasn't in interview (Score:4, Interesting)
I'm not saying it was a lot of work, but it's a quick and dirty way for a small business to get something that's just a little broken on their website fixed.
What's the difference ? (Score:5, Insightful)
Re:What's the difference ? (Score:5, Insightful)
Slashdot relies on "people working for free" too (Score:2)
Isn't that what Redhat's all about? (Score:1)
Or are we talking more of a pandora model, where a portion of the proceeds for where you are drawing support gets paid back to those devs who are providing support?
Always been that way (Score:4)
First the UUCP then the Internet have always depended on some one working for free. Back in the '80 I was routing messages down stream on my Amiga using UUCP. A service I provided for free on software written and provided for free.
The current Internet is no exception. Most of the software that is doing the real work was written for free. I imagine it will always be that way. Someone will do the work to keep the system working.
And you can not earn a living doing OpenSource (Score:2)
Re: And you can not earn a living doing OpenSource (Score:2)
I earn a living writing predominantly open source software. Most every project I work on is thin proprietary layer on top of open source modules that solve the fundamental problems I need solved. My employer doesn't care if I open source work as long as security is addressed.
Re: (Score:2)
Really? Most of my work is done using Open Source stuff and I get paid fine.
They don't work for free! (Score:1)
The vast majority is employed, and it is part of their job! E.g. because they use it.
And the rest also do it, because they get somethig from it. Like tme submitting a patch in my free time, that fixes what bugged my on my home server.
Work is paid. In some direct or indirect way.
The RESULT of the work, is free!
And that is exactly how it should be!
Want more money? Do more work! This is not the Content Mafia! Nor stock trading!
Hell, I do not evem want any money! Because I do not want to work more! I want to li
s/tme/me; s/my on my/me on my/. (Score:1)
Dear Slashdot, please add a preview on mobile.
Oh, and a preferences page too.
And switch to UTF-8. It has been over 25 years!
Discogs / Wikipedia are perfect examples of this (Score:3, Insightful)
... and not just the Internet, but a lot of other work too. It's amazing how much time people willingly and unwillingly volunteer. It's funny because if you asked for money, most people wouldn't give you any but they will give others their time. It's bad because no matter how much time you give, you still have no say in how the project is administered. It's never democratic and there's never any profit sharing, the people at the top take all the cream and yet everyone tells them how great they are!
So many people get easily rich by taking a lot off the top and not paying back the many people who each gave up so much. It's basically modern wage slavery, pay as little as possible in order to profit as much as possible. ;~(
Then don't do it (Score:2)
Back before Wikipedia was the serfdom it has become, and other big content platforms like Facebook, people that were subject matter experts would often (gasp) host their own websites. I know, crazy, right? But that's how we rolled, and the Internet was a place with a much better signal-to-noise ratio, and with a lot fewer ads too.
Remember -- participating on Wikipedia is completely voluntary, as is contributing to an open source project. No one puts a gun to anyone's head and MAKES them contribute. Ther
Re: (Score:2)
Back before Wikipedia was the serfdom it has become, and other big content platforms like Facebook, people that were subject matter experts would often (gasp) host their own websites. I know, crazy, right? But that's how we rolled, and the Internet was a place with a much better signal-to-noise ratio, and with a lot fewer ads too.
Remember -- participating on Wikipedia is completely voluntary, as is contributing to an open source project. No one puts a gun to anyone's head and MAKES them contribute. There is no coercion. So, while I agree that the behavior you describe happens, I see the comparison to "modern wage slavery" as a bit far-fetched. A lot of these contributors do it as a hobby, for example, and they very much enjoy the time they spend.
Wanna control what happens to the content you create? Pick the right license [choosealicense.com], and host in on your own site. All the tools are there -- in fact, they've never been more available and easy to find. There's nothing stopping you.
often it's not practical, like the rest of your argument, clearly, no, it's not really a choice, if you need to contribute in order to further larger goals, they kind of own a part of you
my point is that they take far more than their fair share, they really need to share more to get more ...
Postman (Score:2)
We dumped Curl for Postman several years ago. WAY easier to use, and hey, their developers are paid. :)
- Necron69
Comment removed (Score:3)
Re: (Score:1)
Nothing is for free (Score:2)
But not all forms of compensation are monetary.
Sometimes the person might be seeking fame, or to build a portfolio to get a job later on, or in many, many cases, just for the fun of it.
For example, people that write emulators, in many cases do it for the fun of reverse engineering a closed system and the gratification that comes when the software starts to run better and better, until it gets to a point where everything runs, (including software he don't actually own that just happened to land on the harddr
Mostly right (Score:2)
One problem is that the state of such open source components is hard to assess and it's easy to believe everything is fine with just time-limited volunteers or a small number of paid coders. It takes a lot of time and effort to do things right but since the code is just available it's easy to take but no one wants to pay for maintenance and
Many engineers are paid to work on FOSS (Score:2)
There certainly are many people working on FOSS projects as volunteer/hobby work, and that's awesome. But there are also thousands of engineers who are paid by their employers to work on FOSS projects because those projects are valuable to the employer. For example, numerous companies that utilize Linux pay their engineers to work on it, such as IBM, Google, Samsung and Microsoft as well as hundreds of smaller companies. https://www.zdnet.com/article/... [zdnet.com] . Don't think of FOSS as "hobby" software, think of i
Misleading arguments (Score:2)
which relied on a single full-time developer not making a mistake as they updated and changed that code, used by millions.
OpenSSL might have only 1 full time developer but it also has many part-time developers that lend their skills when needed. This does not take into account that the amount of work required. For example OpenSSL 1.0.2 has about 500,000 lines of code. Also the same criticism could be applied to closed source with the difference being that the public may not know how many developers or lines of code in closed source.
Not people. Kids. (Score:2)
I'm ok with this (Score:5, Insightful)
The alternative is all the code that makes the internet work would be proprietary and locked down.
I think that's why the open source community does this. There is a payoff, it's just not in dollars or food.
They also just enjoy programming I think. I mean who would do such a thing for free if they hated it?
Bottom line, better think carefully about what you're asking for. If you want 'paid for' programming running the internet, better be prepared to not get the source code with it.
This current model works well. It may shaft some people, but I think ultimately we as a species win in the end. I think these selfless people who do all this work for free are the unsung heroes of our era.
OpenSSL was a bad example (Score:3)
OpenSSL was a poor choice for an example. The entire SSL spec is more an example of a bunch of companies getting together with the goal of making something simple virtually impossible to implement for free. I remember when the spec was first made public, there were lots of questions as to why it was so overly complicated, and the spec witten in a way it was very difficult to understand. People who worked on it at Netscape said it was done intentionally, though didn't say why. Though I think it's pretty obvious, and few people would disagree, they were trying to lock out competitors. Had SSL followed similar paths like open source projects, we'd very likely have a much easier spec to work with and lots of open implementations.
Plenty of people are paid to develop FOSS software (Score:2)
I thought large portions were paid for (Score:2)
Re: (Score:2)
They are. The writer is an idiot who doesn't know anything about the subject matter. That is why he writes for a blog.
So what's the alternative? (Score:3)
Downloads want to be free. (Score:2)
The Internet Relies on People Working for Free
Correct. *downloads from Piratebay* ;-)
Expanded conditions (Score:1)
Single Open Source developer called “they&rd (Score:1)
There is no "open-source", that should be Open Source.
“an open-source library called OpenSSL, which relied on a single full-time developer not making a mistake as they updated and changed that code”
“they”, has slashdot been bitten by the PC bug? The developers name is Dr Robin Seggelmann. So unless he's decided to self-identify as 'a
As an open source dev... (Score:2)
...I haven't written much code for free. I mostly wrote open source code because my employer wanted me to (or allowed me to) as part of my job.
I'm sure there are people writing code in their free time, completely unrelated to their jobs, but all the open source devs I know are getting paid, either by working for big orgs that pay them, or by working as consultants.
I can recall (Score:2)
title miss keyword (Score:1)