News for hackers. Stuff that matters.
Re:Sorry everybody, I failed with you by glangdale on Monday June 07, 2021 @08:19AM (#27421665)
Seeing a lot of posts like this. Open source is wonderful in its way, but it's really not sustainable to work on projects that make money for other people - including big commercial interests - when they don't help out in any fashion. I'm not just talking money or contributions. I'm talking about simple acknowledgement: "we use project X" - even privately.

A open source library that I worked on at Intel (the Hyperscan high performance regular expression library) had to shed most of its staff (including all the original folks who worked on it, including me). One of the big contributing factors was a sense that "well, who really uses this". The answer was "tons of people, including some major Intel target customers" but a number of Hyperscan users picked up the library and never told anyone (not asking for public plaudits, but even a private communication would have been something to show our management).

When you can't even say "thank you, we're using your library now, it's great" in a goddamn email, don't be surprised when 75% of the people maintaining and advancing it don't have jobs anymore. Never mind paying money or contributing - even acknowledgement.

Open source is a recipe for burn-out. If something is important to people - especially corporate interests - there needs to be a way of getting paid. Much as I dislike those wacky "free for non-commercial use, otherwise, give me a call" licenses, I'm starting to see the point.

Re:Sorry everybody, I failed with you by altf4 on Monday June 07, 2021 @08:34AM (#27421792)
I agree. I've been working on a Go library for 8 years now that I'm sure is used by quite some people and companies, and I've been close to burnout and letting it go at least twice. I'm super happy when people just "Buy me a coffee"--not for the coffee but for the feedback you get that someone is using your project, so it's valuable for someone. I'm very grateful for that, even without financial support.

I think GitHub should really have a way for users of your repository to somehow illustrate that they're using your project. Maybe that'd even help to get into contact with your users and the companies building solutions on top of your product. Maybe it's just me, but I often feel blind to how and where your project is being used.

EDIT: Typo.

Re:Sorry everybody, I failed with you by supportlocal4h on Monday June 07, 2021 @08:59AM (#27422009)
There are a lot of facets to open source contributions. One big facet is the whole itch-scratching thing. If you know longer itch, stop scratching. That's ok. Maybe when you stop scratching, it will start to itch again for you or for someone else. If nobody steps up, it just means it doesn't itch enough.

Abandonware is not such a bad thing. It served its purpose for a season, then the world moved on. Nobody's out there trying to breath life into the Apollo program. Or into Mosaic. And that's ok. It doesn't diminish how awesome they were at the time.

Re:Sorry everybody, I failed with you by bin_bash on Monday June 07, 2021 @01:39PM (#27425507)
The hard part of OSS management is dealing with change requests. Something comes in and now it's on the maintainer to ensure that the new fix doesn't break anything existing, or the new feature doesn't collide with anything else that comes down the pipe later. It's not work that can be done by volunteers, it's something that can only be done by long-term maintainers.

When I worked on an OSS project I hated getting PRs. They usually wouldn't work for one reason or another and I would have to explain why they were problematic. It took a lot of time out of my day—I would rather people just submit bug reports and feature requests.

Re:Sorry everybody, I failed with you by fourthark on Monday June 07, 2021 @05:34PM (#27427318)
Also it hurts all around to tell a hopeful contributor that their code isn't good enough.

Yes, with hours of effort you can make your review relentlessly positive and constructive, but then it still hurts and they probably don't have the ability to fix it.

You'll have to fix it for them, which is often harder than writing it from scratch.

Re:Sorry everybody, I failed with you by jka on Tuesday June 08, 2021 @04:25PM (#27440298)
Thanks for writing this; it matches an undescribed feeling that I've experienced for a few codebases.

What I'd add in response is that this "change request load" is much easier to manage for small, well-maintained projects with fewer quirks.

And if the entire project architecture can fit within your mental buffer space at one time, then it's much easier and faster to parry those incoming change requests and pull requests into clear, effective feedback and code.

Re:Sorry everybody, I failed with you by rileytg on Monday June 07, 2021 @12:16PM (#27424294)
This applies well for things like a java package where the itchy generally have the skills to scratch. I think of these things as having numerous benefits, namely saves your company/team time; most of the time, in this case I think boo-hoo if the person working tirelessly for no compensation stops doing that... Pay them or do it yourself. (I am currently doing-it-myself with an abandoned java package my team relies on.)

However, this logic fails for situations where the itchy often aren't capable of scratching. For example, a wordpress plugin. In this case, I think it's a grey area. Maybe users should have to pay since they can't write it themselves. But that attitude would still fail for situations where a library is widely used and security patches would be for the "greater good".

Re:Sorry everybody, I failed with you by thefunnyman on Monday June 07, 2021 @01:56PM (#27425766)
In such a case, maybe Wordpress themselves should extend some engineering capacity for maintaining popular OSS plugins for their ecosystem.
Re:Sorry everybody, I failed with you by dimitrios1 on Monday June 07, 2021 @10:56AM (#27423329)
There's also libraries that are simple enough that they just work fine without constant updates. I have numerous libraries that I use that haven't had commits pushed for 2+ years. This is the other aspect: burnout is so rampant because it feels like it never stops and you can come up for air.
Re:Sorry everybody, I failed with you by marlor on Tuesday June 08, 2021 @01:46AM (#27431013)
Burnout is made worse when you take on too many complex interactions and dependencies.

OSS works best when it’s a small project that does a single thing and does it well, but doesn’t rely on too many upstream projects for its functionality.

As soon as the project tries to do too much, it virtually needs a committee to coordinate it all. If it relies on too many upstream dependencies, then the maintainer will be hammered with complaints that “this doesn’t work with version 1.45 of foolib… fix it!”.

But a project that just lives in its own little world, doing its own little job? It’s something you can just maintain and improve at your leisure.

Re:Sorry everybody, I failed with you by dimitrios1 on Tuesday June 08, 2021 @09:55PM (#27443356)
The irony is we demand constant updates, pushes, recent commits, and maintenance, yet we use OSes with libraries and tools that were written decades ago and see little to no updates at times. Some of us go happily along using a decade old version of zlibc, for example. But when it comes to that latest NPM dependency -- if it doesn't have a commit within the last six months, psh! must be abandonware.
Re:Sorry everybody, I failed with you by hinkley on Monday June 07, 2021 @07:23PM (#27428646)
That sounds good in theory but it doesn't compose.

Maybe only a few people are using your library directly, but most use it as part of some larger library. That library has a continuity problem now.

Re:Sorry everybody, I failed with you by umvi on Monday June 07, 2021 @09:26AM (#27422304)
> I think GitHub should really have a way for users of your repository to somehow illustrate that they're using your project.

Well "stars" are kind of like that. Also the insights page tells you how many times your repo is being cloned per day, so that's one metric you can use to see how "used" your project is. You can also search GitHub for the name of your project and see how many other projects are cross referencing it.

Re:Sorry everybody, I failed with you by leejoramo on Monday June 07, 2021 @10:15AM (#27422873)
I am afraid that within GitHub I mostly use stars as a bookmark for projects I find interesting and may want to check out in the future.

If I fork a project I am more likely to actually be using it, although in fact I have plenty of forks from simply evaluating or playing with a project

Re:Sorry everybody, I failed with you by exciteabletom on Monday June 07, 2021 @10:55PM (#27430153)
>I am afraid that within GitHub I mostly use stars as a bookmark for projects I find interesting and may want to check out in the future.

Wouldn't it make more sense to use the "watch" button for this?

Re:Sorry everybody, I failed with you by gkilmain on Monday June 07, 2021 @09:30AM (#27422353)
"stars", at least from my perspective, doesn't map to usage. I've stared plenty of projects I don't use. I like the latter two metrics - thank you for sharing!
Re:Sorry everybody, I failed with you by johnnyanmac on Monday June 07, 2021 @07:21PM (#27428626)
Devil's advocate: no action short of landing your own project will prove that you use a library. I've donated to stuff like Godot (which I have yet to open myself) and Blender (which I only know the bare basics of; I haven't even tried the new UI overhaul) years back because they are projects I appreciate an open source alternative for these very complex problems.

of course, giving cash is a much bigger gesture than just pressing a star button, but it sounds like the star button is closer in vein to the kinds of acknowledgement people are asking for here.

Re:Sorry everybody, I failed with you by jeffasinger on Monday June 07, 2021 @09:47AM (#27422561)
One thing you may encounter is that a large company may be using it for many things internally, and that still shows up as just a handful of clones, because they have some central artifact caching service in place.
Re:Sorry everybody, I failed with you by dkersten on Monday June 07, 2021 @10:48AM (#27423253)
The problem with stuff like stars or even lists of "who uses this" is that they need to be refreshed every so often. Just because someone used your project ten years ago, doesn't mean they're using it today. Maybe a list with a "latest update" date and gently asking and reminding people to update it each year if they're still using the project would help...

As for cloning, I don't clone projects I use every day. Maybe I cloned them once a year ago. Maybe I'm using a package from somewhere and not interacting with your repo at all.

The cross-referencing sounds like a useful metric though, at least for open source use, but many projects are more useful in non-open-source environments (eg how many open source projects are using something like http://riemann.io/ ?)

Re:Sorry everybody, I failed with you by scrps on Monday June 07, 2021 @10:13AM (#27422844)
It would be nice to have a similar system to the language metric at the bottom of a repo, have something like a library metric that list what external libraries a project uses and feed those metrics back to the maintainers.
Re:Sorry everybody, I failed with you by nitrogen on Monday June 07, 2021 @11:58AM (#27424077)
GitHub does show a dependency list in the sidebar for some projects.
Re:Sorry everybody, I failed with you by swiftcoder on Monday June 07, 2021 @12:54PM (#27424861)
Unfortunately, they don't have dependency plugins for a bunch of popular languages. Even languages with well-structured dependency tracking like Rust.
Re:Sorry everybody, I failed with you by toastal on Monday June 07, 2021 @10:49AM (#27423257)
The social stars aspect of GitHub is what makes it toxic. I would support more visibility for open, not centralized initiatives like humans.txt and contribute.json (https://www.contributejson.org/).
Re:Sorry everybody, I failed with you by usrusr on Monday June 07, 2021 @08:47AM (#27421903)
In the Java world we have the Maven repository dependency aggregators like mvnrepository.com that accidentally serve as some kind of citeseer equivalent. I assume similar things exist for the package managers of other languages as well?

But obviously most commercial usage remains invisible. I could imagine a hybrid cultural/technological approach were dev teams publish/are allowed to publish at least usage metadata were they can't publish source (or actually contribute).

There's a huge tie-in with security, I remember heated discussions were one side tries to establish this as an audit mechanism ("how vulnerable is product x really, in terms of outdated dependencies?") and incentive for updating, while the other side is crazy scared of punishing a list of potential attack surfaces. Perhaps the implied attribution benefit should become part this discussion as well?

Re:Sorry everybody, I failed with you by josephg on Monday June 07, 2021 @09:04AM (#27422055)
For javascript packages, npm lists which other packages which depend on any given package, and how many times a package was downloaded in the last week. That gives you a rough sense of usage, but it can also be super mysterious.

As an example, here's a package I wrote which I haven't touched in 3 years: https://www.npmjs.com/package/jumprope

There are no projects on npm which depend on this, and yet it gets downloaded about 3000 times per week. Who's using it? I have no idea. Are they running into any problems? I suppose not, I mean, there aren't any issues on github. Its kinda spooky.

Re:Sorry everybody, I failed with you by usrusr on Monday June 07, 2021 @10:09AM (#27422802)
Thanks, just like I expected. Hopefully every at least remotely modern dependency/package manager has some sort of citeseer equivalent in its ecosystem.

And your last paragraph nicely illustrates the blindness we get from closed projects/products not publishing their dependency metadata. I suppose that for client side js a tiny subset of usage stats could be generated by CDN distribution, but repackaging is a thing (and for good reason, in many cases)

Re:Sorry everybody, I failed with you by rightbyte on Monday June 07, 2021 @09:44AM (#27422518)

   Rope took 5610 ms. 0.001122 ms per iteration, 891k iterations per second
   JS toString took 3463 ms. 0.003463 ms per iteration, 288k iterations per second
I guess you have a typo there in total time?
Re:Sorry everybody, I failed with you by ratww on Monday June 07, 2021 @09:09AM (#27422107)
You can possibly find some users in Github: https://github.com/search?q=jumprope+filename%3Apackage.json...
Re:Sorry everybody, I failed with you by ianwalter on Monday June 07, 2021 @09:37AM (#27422425)
I really wish GitHub would invest more in the dependency graph, like allow you to sort by stars at least: https://github.com/josephg/jumprope/network/dependents
Re:Sorry everybody, I failed with you by josephg on Monday June 07, 2021 @09:15AM (#27422185)
Oh good idea! It looks like Github also tracks a project's dependancy tree explicitly, though those 3000 downloads per week remain a mystery:

https://github.com/josephg/jumprope/network/dependents

Re:Sorry everybody, I failed with you by ianwalter on Monday June 07, 2021 @09:41AM (#27422480)
I've heard that the vast majority of those downloads are from CI systems. It would be cool if GitHub could draw anonymous metrics from GitHub Actions and help with this mystery.
Re:Sorry everybody, I failed with you by bachmeier on Monday June 07, 2021 @09:25AM (#27422298)
> I've been close to burnout and letting it go at least twice

Why don't you? That's how you get people to step up.

Re:Sorry everybody, I failed with you by andrenatalbr on Monday June 07, 2021 @06:43PM (#27428230)
Github allows any repo owner to adda donation button. That should be a more widespread practice.
Re:Sorry everybody, I failed with you by indigochill on Monday June 07, 2021 @09:21AM (#27422240)
> I think GitHub should really have a way for users of your repository to somehow illustrate that they're using your project

I kind of use forking that way (although more when I like a project, it's not necessarily a promise that I'm using it anywhere). This ensures that I have a copy of the project in the state that I originally liked. Then if the project is either (a) taken in a disagreeable direction or (b) deleted, I still have my local copy. I can also always update from upstream if future development occurs that I want to benefit from.

That said, I don't fork all the open source packages I use, although maybe I should.

Re:Sorry everybody, I failed with you by throwaway894345 on Monday June 07, 2021 @08:43AM (#27421877)
What’s the library, out of curiosity?
Re:Sorry everybody, I failed with you by sillysaurusx on Monday June 07, 2021 @12:17PM (#27424298)
I was recently shocked to discover that sindresorhus, one of the most prolific oss devs of all time (I think), only has around $14k/yr of app revenue. It sounded like he was saying that it was a majority of his income, so I pressed him how he could possibly live on it. He said he had GitHub sponsorships and open collective donations, and then mentioned he was living in a country with low expenses.

I ended up feeling... amazed, really. I was going to say sad, but if the most prolific oss dev can’t make more than an entry level salary from 2008 on community support alone, it’s not sad — it’s simply how it is.

People need to think of open source as something they do for themselves. I put stuff out for people to use. You don’t like it, you can use something else. I try to give as much help as I can, but only because it makes me happy to do that.

The recipe for burn out is, you’re not putting yourself first. You should! Most people do open source the way a jazz pianist does a jam session on the weekends, but it sounds like your typical jazzist (jazzer?) ends up happier than most of us. It’s worth taking a hard look at why.

Don’t do it to yourself. Life’s worth more. I understand why they left a lengthy apology here, saying “I let the community down” and such, but it’s just not true. Everyone who makes their code available for others isn t a letdown — you’re a hero to 12yo me, who would’ve given anything to get a glimpse of any closed-source gamedev engine. That’s what OSS is all about: letting people build on your work, not working yourself to death for other people.

Re:Sorry everybody, I failed with you by oh_sigh on Monday June 07, 2021 @01:21PM (#27425247)
It seems that he isn't really trying to make more money. Maybe I'm misinterpreting his words from his site:

https://blog.sindresorhus.com/answering-anything-678ce562379...

> How do you make a living if you don’t have a job and don’t take donations?

> I don’t make a living, currently. I have some money saved up. I don’t really care much about money or material things, don’t use much money, and don’t have a lot of monthly expenses.

> Do you enjoy being homeless?

> Definitely. It’s nice being free to travel anywhere at any time. I don’t really care much about material stuff either, so I have everything I need and care about in a small backpack.

> How to be rich?

> You don’t want to be rich — You want to be happy.

Re:Sorry everybody, I failed with you by jiofih on Monday June 07, 2021 @08:24AM (#27421716)
> there needs to be a way of getting paid

You said you worked on the library at Intel. Doesn’t that qualify as getting paid for your work?

That’s not the usual setup when developers talk about getting paid for their OSS contributions, usually off the clock, so its not clear what the lesson is here besides politics/resourcing at big co (which is a real but distinct problem).

This situation was supposed to be where OSS shines - instead of a dedicated team subject to the will of a single private corporation, a project should have multiple contributors, working on their employers’ time - then there is no central team to be disbanded.

Re:Sorry everybody, I failed with you by glangdale on Monday June 07, 2021 @08:34AM (#27421799)
Fair enough - my complaint is a bit too compressed. The point here is that my experience at Intel led me to realize that corporate OSS users will take your library in secret and not even tell you - much less publicly acknowledge it, much less contribute or help support it. Obviously I'm not expecting to be paid extra while at Intel because folks are using a library.

It's just rather discouraging from the perspective of working on anything else OSS as an independent developer - unless it's a pure passion project. Given that the stuff I'm interested in often tends to wind up being hauled into high-performance infrastructure that's kind of important to bigcos, it's a bit depressing.

The whole multiple contributors thing is a great theory and works for some high-gloss, high-profile projects. There's a huge tail of OSS where the expertise just isn't there and most companies just want to free ride.

Re:Sorry everybody, I failed with you by barrkel on Monday June 07, 2021 @09:50AM (#27422591)
> You said you worked on the library at Intel. Doesn’t that qualify as getting paid for your work?

It just shifts the problem along; instead of getting paid, you need to justify to Intel why they should pay you. Showing that you're keeping customers happy, building Intel brand value etc. can be part of that, but only if they give you feedback.

Re:Sorry everybody, I failed with you by unreal37 on Monday June 07, 2021 @08:27AM (#27421733)
It was an Intel project. https://github.com/intel/hyperscan/
Re:Sorry everybody, I failed with you by mellavora on Monday June 07, 2021 @09:24AM (#27422289)
Need to justify the time spent on it to management.
Re:Sorry everybody, I failed with you by watwut on Monday June 07, 2021 @09:46AM (#27422537)
Based on FOSS surveys I have seen, majority of OSS contributions are paid for that way. The off the clock for free contributions are smaller part of it all.

I think the off-the-clock long term OSS maintenance is rare, because it is actual work. And contrary to stereotype, no matter how passionate you are, you will burn out if you work two full time jobs at the same time.

Re:Sorry everybody, I failed with you by op00to on Monday June 07, 2021 @08:25AM (#27421722)
Not always. Might be a personal project.
Re:Sorry everybody, I failed with you by Cthulhu_ on Monday June 07, 2021 @08:54AM (#27421971)
I feel like Github and co could do a LOT more to help open source project maintainers and contributors rewarded.

They can offer a new subscription model for people with expendable income and companies with benefits, on a per user basis instead of a per project one.

They can offer monetizing issues, e.g. promoting a question or issue report with an X amount of currency.

OS maintainers can create a bot that asks people to contribute financially or to reach out to their employer to do so.

Github can push their sponsors program more, and aim it at companies / "enterprise" sponsors.

Re:Sorry everybody, I failed with you by lolsal on Monday June 07, 2021 @10:32AM (#27423060)
A counter-argument to these ideas is that because it's open source, I'd just fork whatever I wanted to use and re-host somewhere else.

Maybe if it was an optional and project-oriented patreon-style?

Re:Sorry everybody, I failed with you by llaolleh on Monday June 07, 2021 @10:28AM (#27423022)
These are great ideas. You should shoot the higher ups an email and a link to the thread.

Your suggestions seem like a win win for Github and the hardworking OSS maintainers.

Re:Sorry everybody, I failed with you by sdenton4 on Monday June 07, 2021 @11:34AM (#27423787)
Monetizing issues would be a great move.
Re:Sorry everybody, I failed with you by supportlocal4h on Monday June 07, 2021 @09:05AM (#27422069)
Sounds like you've got some ideas. That's cool. Take a risk and try to run with some of your ideas. Maybe you can help them grow legs.

You could just leave it up to somebody else to solve, but if you've got viable ideas, give it a shot.

Re:Sorry everybody, I failed with you by halfdan on Tuesday June 08, 2021 @06:46AM (#27433221)
I'm so sorry to hear that has happened to the team behind hyperscan. It's truly a fantastic library and has helped us speed up some of our regex heavy workloads write drastically. I even spent some time writing about hyperscan both internally (at $dayjob) and externally.

Thanks for your work on hyperscan! I think I'll identify a few other libraries that we use and reach out to their developers - it's a good reminder to not take everything for granted.

https://geekmonkey.org/regular-expression-matching-at-scale-...

Re:Sorry everybody, I failed with you by mumblemumble on Monday June 07, 2021 @10:03AM (#27422728)
I've actively resisted open sourcing some things I've written at work - including stuff that I'm sure others would like - precisely because of fears that it would be a career-limiting move. For my employer, these libraries are only valuable to the extent that they help us build things for which we can charge money. An open source library would not be one of those things, but it would take time (and therefore company money) to maintain such a thing. So putting myself in a position to be maintaining open source software on company time has the potential to greatly reduce my value to the company.
Re:Sorry everybody, I failed with you by snth on Monday June 07, 2021 @10:23AM (#27422945)
I think getting your name and work out in the world with open source work is a career _advancing_ move.
Re:Sorry everybody, I failed with you by mumblemumble on Monday June 07, 2021 @10:56AM (#27423328)
I've honestly never been at a job interview where people gave a crap about my open source contributions. They're typically much more interested in hearing war stories from the closed source projects I've worked on.

The thing about open source projects is, they tend to be slightly generic things like "file format," "widget library," or "machine learning algorithm" that most companies see as the kind of thing they can typically get for free from open source. (They're not wrong there - the fact that we're talking about my open source contributions here makes it almost tautological.) They also tend to involve the sorts of generic programming skills that, by virtue of being stuff that we all know at least somewhat well, aren't all that valuable. Supply and demand works with job skills, too.

By contrast, my commercial work tends to involve a lot of specialized knowledge that's quite uncommon, and also tends to produce the kinds of software that people are quite happy to pay a lot of money for.

Re:Sorry everybody, I failed with you by autarch on Monday June 07, 2021 @11:05AM (#27423421)
> I've honestly never been at a job interview where people gave a crap about my open source contributions. They're typically much more interested in hearing war stories from the closed source projects I've worked on.

Counterpoint - I have. Many times.

I created some Perl libraries (most notable <a href="https://metacpan.org/dist/DateTime">DateTime</a> and <a href="https://metacpan.org/dist/Log-Dispatch">Log-Dispatch</a>) that were used by a huge percentage of companies using Perl for applications (as opposed to simple scripts or sysadmin). This often came up in interviews, and I'm sure it helped me get more and better offers.

Nowadays, as fewer companies are using Perl for applications, it's probably less helpful, but it doesn't hurt.

Re:Sorry everybody, I failed with you by deckard1 on Monday June 07, 2021 @01:08PM (#27425084)
To be fair, that's like the guy that wrote moment-js or jQuery. I've worked at a number of Perl-based companies and every single one used DateTime (I'm a huge fan, btw). Something like that is going to be noticeable on a resume. Assuming they have some experience with Perl.

There was a company I know of that was advertising in their job postings that the guy that wrote Perl's DBI once worked for them or was their CTO or whatever. That was about 6 years ago, so not that far off.

Re:Sorry everybody, I failed with you by mumblemumble on Monday June 07, 2021 @11:10AM (#27423498)
Ha. I had actually thought about mentioning that this situation seemed to be very different 20 years ago, but decided I had already done enough blathering.

But, anyway, yeah - I think that this was different 20 years ago, back when open source hadn't quite completely disrupted the software industry and companies didn't yet understand the economics of open source.

Re:Sorry everybody, I failed with you by johnnyanmac on Monday June 07, 2021 @07:36PM (#27428767)
I mean, I worked with someone who creates a very high profile OSS project, and I'm sure it's a big reason he got hired to where he is.

I'll never say OSS is an optimal career path unless you are doing something extremely specialized (which to be fair, he is). But it sure can open doors for you even today if that's something you're passionate in. For me, I got around without any OSS, so it's more like a post-career plan now to help out some beloved repos.

(as long as you're not stupid, like showing your botting repository to an online game studio).

Re:Sorry everybody, I failed with you by autarch on Monday June 07, 2021 @11:15AM (#27423557)
This still helped me as recently as 2017, so it's not like this stopped being true 20 years ago.
Re:Sorry everybody, I failed with you by loup-vaillant on Tuesday June 08, 2021 @10:51AM (#27435943)
> I've honestly never been at a job interview where people gave a crap about my open source contributions.

They gave a crap about mine, I believe for two reasons: first, I put it in the middle of my CV, at the same level as my regular job. This basically forces everyone to talk about it. Second, Monocypher is a crypto library, and cryptography tends impress people.

Re:Sorry everybody, I failed with you by pizza234 on Tuesday June 08, 2021 @04:31AM (#27431911)
I can't speak for other companies, but as a person involved in hiring, open source is very valuable to me.

It's not valuable in terms of potential to market/usefulness/popularity, rather, because I can see very clearly how a person designs/writes code, and how they solve problems, when they have plenty of time; I can also see other non-technical aspects, like how they structure their git history (which, to me, has lot of signals).

People (rightfully) dislikes to show their capacity under pressure; open source is the way to show it without pressure :)

Re:Sorry everybody, I failed with you by jcadam on Monday June 07, 2021 @09:25AM (#27422293)
A lone developer can not maintain more than one or two open source projects at a time. I know for me, if I don't see any traction at all in the community once I get a project to some sort of MVP state, I will lose interest and move on. My github has many dead 1.0 projects :)
Re:Sorry everybody, I failed with you by j1elo on Monday June 07, 2021 @01:22PM (#27425260)
Maybe an easy solution is to do the thing everybody seems to discourage: add a clause to your preferred OSS license, stating that usage of the code is subject to sending a mandatory thank-you email.

That change alone might be enough to break the fragile conditions that allow the license to be considered Open Source... but who cares, the mental health and happiness of OSS devs affected by the difficulties mentioned in here is more important than the technicalities of what could happen by a small clause addition.

Re:Sorry everybody, I failed with you by pizza234 on Tuesday June 08, 2021 @04:34AM (#27431927)
That's Postcardware!¹ :)

I remember using one, but I not exactly which one; it's not in the Wikipedia list.

¹=https://en.wikipedia.org/wiki/Postcardware#Postcardware

Re:Sorry everybody, I failed with you by pizza234 on Tuesday June 08, 2021 @06:27PM (#27441887)
Found: it was (not anymore) Exact Audio Copy¹.

¹=https://www.exactaudiocopy.de/en/wp-content/uploads/2007/03/...

Re:Sorry everybody, I failed with you by darau1 on Monday June 07, 2021 @09:09AM (#27422110)
Or, if you can't give the dev some money, or a thank-you, fix it yourself. I think that's supposed to be the point of open source.
Re:Sorry everybody, I failed with you by lamontcg on Monday June 07, 2021 @01:03PM (#27424981)
I'd really like GitHub to have the option of open sourcing your work but both being able to turn off pull request and be able to limit PRs and issues to trusted contributors. Open source / closed contribution on an individual level.

I like the project I'm working on now, but if I release it publicly I don't want to deal with 98% of the possible users. I'm mostly worried about the idea that the itch I want to scratch will turn out to be popular, because open source is mostly horrible.

Re:Sorry everybody, I failed with you by lumost on Monday June 07, 2021 @09:54AM (#27422627)
For a while Open Source was a great way to project skill onto employers, and employers reaped recruiting benefits for having a large open source portfolio. This extended to the point that companies would accept internal inefficiency to support an open source release of a portion of their code. This has detectably changed in the last 5 years or so as getting a top project on github has both become more difficult as well as a more common bragging right. Everybody has some open source, so the marginal benefit to a company of releasing another project is low.

It would be great if there was a method for privately tracking who uses what libraries so that the marketing/support model could be used. Tons of companies use Tensorflow to run on TPUs, but Google doesn't know if tons means 90% of their cloud customers or 5% ( unless they put library tracking directly into the TPU which ... is possible)

I'd love to see a feature on Github for tracking dependents of a project. I'd also bet that most major firms would be willing to allocate a small funding level to ensure that lynchpin dependencies such as OpenSSL, git, maven and other projects remain viable - after all it's probably cheaper than migration later!

Re:Sorry everybody, I failed with you by usrusr on Monday June 07, 2021 @08:34AM (#27421794)
Oh, that scenario, retreating corporate sponsor would probably not have retreated if only usage was more visible, that must have been very frustrating. Almost seems as if the odd occasional visibility boost from some heavy bug or exploit could have saved it. Were Oscar Wilde and PT Barnum secretly open source visionaries?
Re:Sorry everybody, I failed with you by glangdale on Monday June 07, 2021 @08:37AM (#27421833)
One thing I found immensely frustrating was that occasionally other projects at Intel (not mentioning names) would wind up completely fucking up by, say, building the wrong thing, then they would do some heroic 8-week "save" of the mess that they made, and wind up getting Major Corporate Recognitions.

A bodgy, high-touch system that required endless customization and lots of meetings would become a high profile project that could ultimately get the corporate equivalent of high fives all around. Meanwhile, if you ship a library that Just Works, people quietly link it into their product and move on with their lives.

Re:Sorry everybody, I failed with you by usrusr on Monday June 07, 2021 @12:06PM (#27424179)
Sorry to hear that, I was hoping that my "no such thing as bad publicity" musings were merely crazy what-ifs, not a reflection of your reality.
Re:Sorry everybody, I failed with you by pkaye on Monday June 07, 2021 @01:44PM (#27425579)
That has been my own experience too. The heroics to fix messes are given more recognition than a properly run projects. One company would actually give quarterly awards be those who did heroics.
Re:Sorry everybody, I failed with you by pjmlp on Tuesday June 08, 2021 @02:27AM (#27431245)
Unwilligness to pay for developer tools or desktop software is what made me gave up and just focus on Apple, Google, and Microsoft platforms.

I rather work for ecosystems where customers see a value that developers keep their job.

Re:Sorry everybody, I failed with you by glangdale on Tuesday June 08, 2021 @02:58AM (#27431408)
Andy Gocke put it best, on Twitter:

"Developer tools seemed like a good industry to be in, "sell shovels in the gold rush" and all, but it turns out developers prefer to dig for gold with their teeth."

Re:Sorry everybody, I failed with you by pjmlp on Tuesday June 08, 2021 @05:37AM (#27432256)
Yeah I love the quote, specially the irony wanted to be paid, while unwilling to pay the work of others.
Re:Sorry everybody, I failed with you by gamerDude on Monday June 07, 2021 @01:03PM (#27424995)
I'm curious. Is there a reason to not build in some sort of ping for the software being used? Essentially doing analytics for open source usage so you can monitor how many people use it?

Obviously there are some potential privacy issues here, but adding it to the README and doing a single ping on use seems like not too bad a compromise to keeping open source projects alive.

It won't be 100% accurate due to offline use or available to many open source software projects due to their use case, but most applications would probably connect.

Re:Sorry everybody, I failed with you by glangdale on Tuesday June 08, 2021 @03:02AM (#27431426)
Surprise telemetry is deeply unethical. Putting it in the README is borderline OK, I guess. However, even supposing it's OK, a "single ping on use" is only really feasible if the system has "main()" and some reasonably persistent usage. If you're a small tool - or a library, like we were, "single ping on use" might result in thousands of systems "beaconing" back to home base per hour.

For the area we were in (pattern matching is basically computer security-adjacent), this would have been equivalent to shipping malware in terms of sheer career-destroying potential.

Not everything is a long-running desktop app.

Re:Sorry everybody, I failed with you by spockz on Monday June 07, 2021 @06:42PM (#27428217)
Generally apps that send telemetry get a lot of flak here. Even if mentioned in the docs/faq.
Re:Sorry everybody, I failed with you by throwkeep on Monday June 07, 2021 @11:10AM (#27423501)
So true, it's really taken for granted. Especially these days with Github and package managers which make it so easy to end up incorporating a dozen or more 3rd party libraries. There's something impersonal about it, and trivializes the amount of sweat that was poured into the code you're npm installing.
Re:Sorry everybody, I failed with you by sebastianhoitz on Monday June 07, 2021 @08:57AM (#27421998)
Totally agree! That's why I want to help open source maintainers monetize the ecosystem they have built. The first step: Sell add-on products/plugins/tools with a super easy Checkout paywall: https://basetools.io
Re:Sorry everybody, I failed with you by epmaybe on Monday June 07, 2021 @08:58AM (#27422004)
Feels like a great opportunity for Github or another website to have these sort of analytics. Seems like quite the complicated task tho. Start small?
Re:Sorry everybody, I failed with you by mdtusz on Monday June 07, 2021 @01:33PM (#27425417)
Rather than centralizing on GitHub, this seems like something that could be well suited as a `.well-known` url websites/companies could use, then anyone/everyone could aggregate or just inspect what is being used.
Re:Sorry everybody, I failed with you by unreal37 on Monday June 07, 2021 @08:25AM (#27421726)
You didn't have any way of knowing who was using your library? Any way of communicating with them? A survey even? Download numbers?
Re:Sorry everybody, I failed with you by glangdale on Monday June 07, 2021 @08:29AM (#27421761)
Once it's up on Github and out there, you don't really have any control. It's not like we were keen to put big barriers on the 'try it out' side. I didn't have some mad keen quest to be able to communicate to management "hey, someone from A----- or H----- downloaded our library". That's not that interesting. A lot of people kick the tires.

What I did kinda want to know is if a major Intel customer put our library into production. Sometimes we figured this out by detective work - e.g. one of our staff had a bunch of custom standing google searches hooked up to an RSS feed that would often find big vendors handing out paraphrased versions of our documentation to explain which regex patterns were supported.

Re:Sorry everybody, I failed with you by im3w1l on Tuesday June 08, 2021 @06:36AM (#27433041)
That's an interesting nuance I never considered.
Re:Sorry everybody, I failed with you by hinkley on Monday June 07, 2021 @07:12PM (#27428537)
I think Richard Stallman's cynicism about licenses was misplaced 30 years ago, but that the tide is turning.

I do prefer to work on libraries that are available for commercial work. But I also cannot get my employers to pay for said libraries. Which is how many of us started using OSS in the first place - because nobody could smack us with a checkbook and say no.

Re:Sorry everybody, I failed with you by tester34 on Monday June 07, 2021 @08:37AM (#27421824)
that's why telemetry is imporant

If I were doing serious OSS I'd really hard consider adding just something like a once-a-week ping just to be aware of users count

ofc with an ability to disable it

Re:Sorry everybody, I failed with you by glangdale on Monday June 07, 2021 @08:40AM (#27421848)
SaaS or something explicitly that people know will 'phone home' is one thing, but putting unexpected telemetry into a library would be staggeringly unprofessional.
Re:Sorry everybody, I failed with you by wrycoder on Monday June 07, 2021 @08:50AM (#27421943)
There is the Debian popularity contest: popcon.debian.org , which tracks how many Debian users have a given package installed.
Re:Sorry everybody, I failed with you by account42 on Tuesday June 08, 2021 @10:13AM (#27435453)
popcon is intirely opt-in though, quite different from automatic telemetry that the user doesn't even knwo about
Re:Sorry everybody, I failed with you by n_marcetic on Tuesday June 08, 2021 @04:42AM (#27431959)
Not really, there is a lot of projects doing this as an anonymous statistic, for example InfluxDB sends anonymous statistics about your InfluxDB instance to their server. This way they have overview/statistic of usage (they are visualize it on word map, looks amazing), together with data like OS, version you use etc... You can disable this in config https://influxdbcom.readthedocs.io/en/latest/content/docs/v0...
Re:Sorry everybody, I failed with you by csharptwdec19 on Tuesday June 08, 2021 @03:21PM (#27439607)
Frankly, there could be some value to OSS contributors in saying 'There is Telemetry' very up front, but also in the same breath telling people that instructions for disabling Telemetry is in the Docs.

Could help lower the number of GH issues that are filed because people don't read said docs...

Re:Sorry everybody, I failed with you by ergot_vacation on Monday June 07, 2021 @12:14PM (#27424265)
I've long believed "open source" is for suckers for exactly this reason. Literally being open source, having the code open for review, isn't a problem. But usually "Open Source" also ends up meaning free as in beer, for EVERYONE, whether you're some college student or a billion dollar company.

The only sane, healthy, sustainable license is the "wacky" one you describe: individuals (and possibly even (very) small businesses) can use it for free. Everyone else needs to pony up. It's absurd that a ton of the software allowing giant corporations to run day-to-day is not only created but ACTIVELY MAINTAINED by an individual or groups of individuals for free, as if they were running a soup kitchen. Microsoft, Amazon and Google are not homeless. They can, and should, pay the people that make the software that keeps them going.

"But if it's open source, couldn't they just fork it and keep using that for free?" Yes, but a. not legally, if the terms forbid it and b. They would now have to find a new group of people to maintain the code, after just creating a bunch of ill-will in everyone in that space. In the end nothing is absolute: you can always just pirate closed-source commercial software too. But doing so has serious negative consequences.

Re:Sorry everybody, I failed with you by dabockster on Monday June 07, 2021 @02:33PM (#27426271)
> "open source" is for suckers

First time I've heard that on HN ever. This needs to be common knowledge so more people realize how valuable they really are.

Re:Sorry everybody, I failed with you by CaptArmchair on Tuesday June 08, 2021 @03:43AM (#27431658)
"Opens source" isn't a business model.

At the end of the day, it boils down to a choice as to how you setlle the intellectual property rights which derive from your creative work. Either you restrict the use, sharing and altering of your work by others; or you give a limitless license and anyone is free to do whatever.

Putting your code out there for free redefines the relationship between you and the users of your code. And it does so at both sides at the same time. It's the latter part which usually tends to be forgotten.

As a developer, sharing your work under an open source license is not an obligation to provide premium support. Or any a support at all, for that matter. All you did was share your work, others are free to either pick it up and use it, or walk past and choose something else.

As a user, an open source license doesn't come with a warranty, nor does it imply that you are entitled to support from the maintainer. All you get from an open source license is the freedom to use, adapt and share the software under a similar license.

It means that maintainers of open source projects are well within their rights to say "No. I'm not going to do that." to whatever request you submit to them. Whether that's an issue queue or an e-mail.

When a maintainer receives a request to add a complex feature or fix a complex bug and the request starts with "We use your code at our business / company / organization..." then it's perfectly acceptable to reply with "I would love to. Please contact me at my e-mail address and I'll send you my offer." As a maintainer, open source still leaves you free to charge for any support people solicit with you. You're even free to differentiate between "this is what I'm willing to do in my spare time, this is what I'm willing to do for a price."

The big question, then, is: Why don't open source maintainers do this?

That's where the answer gets complex. For instance, the jump from side project to sustainable income is difficult. Not all projects would yield enough support / servicing work. And not all projects are interesting enough to turn into a full time job. Depending where you live, making a little extra income from a side project may even get taxed away, making it just not interesting to turn it into a side business.

So, why don't maintainers then just refuse largish questions if they can only work on a project in their spare time? I suppose that's the hard part: publish creative work means putting a part of yourself out there. When facing an audience, being able to take a step back from criticism and feedback is probably the hardest part to creative work. There's all sorts of rationalizations one makes to defend a perceived requirement or obligation to keep working on open source projects, even when it's to one's own detriment. Learning how to deal with that in a healthy manner takes time and experience.

Re:Sorry everybody, I failed with you by WalterBright on Monday June 07, 2021 @11:11PM (#27430239)
A lot of open source developers leverage their contributions into high paying jobs they never could have gotten otherwise.
Re:Sorry everybody, I failed with you by pjmlp on Tuesday June 08, 2021 @02:29AM (#27431259)
Just like a couple of street musicians happen to hit gold, the large majority doesn't.
Re:Sorry everybody, I failed with you by WalterBright on Tuesday June 08, 2021 @03:11AM (#27431482)
The implication is that the OSS contributor has to be good. The same with street musicians.

I once had the pleasure of encountering some street musicians that were very, very good. I bought their CD out of their suitcase. It remains one my favorite CDs. Pludo's "The Only Thing Certain Is The Future".

Sadly, they never made it.

The large majority of street musicians are worthy of a tip, but I'll pass on their CD.

P.S. It's a lot easier to make money as programmer than a musician. You don't have to be anywhere near the top 0.01% to have a good career.

Re:Sorry everybody, I failed with you by pjmlp on Tuesday June 08, 2021 @05:40AM (#27432273)
Only if living in tier 1 countries, I can assure you there are countries where both professions have equal chances of success, and probably the musicians get the upper hand on opportunities.

In many of such places you will probably live better from tourist tips than trying to make it as programmer.

Re:Sorry everybody, I failed with you by WalterBright on Tuesday June 08, 2021 @01:09PM (#27437903)
That's no longer true in these days of working remotely.
Re:Sorry everybody, I failed with you by pjmlp on Tuesday June 08, 2021 @02:46PM (#27439209)
To work remotely, there are certain requirements on the life pyramid that need to be fulfilled.

It starts by living on a country whose technology infrastructure makes it possible at all.

Then it follows on how much the tier 1 customers are willing to pay to their offshored devs, with the race to the bottom on the dollar per hour rate.

There is also the culture of the country, if programming is seen as a servant job only used as stepping stone for a real job, or if it is seen as master of universe Silicon Valley style.

Working as software developer is privilege, not seen through the same lens across the world.

Re:Sorry everybody, I failed with you by duxup on Tuesday June 08, 2021 @12:18AM (#27430597)
I don't doubt it could help but these are pretty talented people in the first place.

I'm not sure they need an OSS project to succeed, or that they would do any differently than if they hadn't.

Re:Sorry everybody, I failed with you by WalterBright on Tuesday June 08, 2021 @12:34AM (#27430664)
OSS is a shortcut to career advancement if your resume is not the best. I know people who have done very, very well via contributing to Open Source.
Re:Sorry everybody, I failed with you by apocalypstyx on Monday June 07, 2021 @01:46PM (#27425628)
> The only sane, healthy, sustainable license is the "wacky" one you describe: individuals (and possibly even (very) small businesses) can use it for free. Everyone else needs to pony up. It's absurd that a ton of the software allowing giant corporations to run day-to-day is not only created but ACTIVELY MAINTAINED by an individual or groups of individuals for free, as if they were running a soup kitchen. Microsoft, Amazon and Google are not homeless. They can, and should, pay the people that make the software that keeps them going.

> "But if it's open source, couldn't they just fork it and keep using that for free?" Yes, but a. not legally, if the terms forbid it and b. They would now have to find a new group of people to maintain the code, after just creating a bunch of ill-will in everyone in that space. In the end nothing is absolute: you can always just pirate closed-source commercial software too. But doing so has serious negative consequences.

This is neither free nor open by either the OSI or the FSF's definitions.

The real problem is that there is a fundamental crisis at the intersection of capitalism and human freedom/autonomy that may be impossible to resolve.

Re:Sorry everybody, I failed with you by dabockster on Monday June 07, 2021 @02:40PM (#27426349)
> This is neither free nor open by either the OSI or the FSF's definitions.

In the famous words of Peter Griffin, "OH MY GOD WHO THE [expletive] CARES?!!"

If someone isn't being paid for their work, then any version of OSS isn't really sustainable long term.

Re:Sorry everybody, I failed with you by apocalypstyx on Monday June 07, 2021 @05:41PM (#27427422)
> In the famous words of Peter Griffin, "OH MY GOD WHO THE [expletive] CARES?!!"

The definitions of these terms have existed for decades. Trying to confuse or conflate them is just a slight of hand to generally disingenuous ends. Very little stops people from selling products under whatever terms they want. If they are honest, they can call their product what it is: proprietary. Otherwise it is just using the term 'open' to virtue signal. So 'open' becomes the new 'green'.

> If someone isn't being paid for their work, then any version of OSS isn't really sustainable long term.

Exactly my point.

FOSS (for the most part) can't achieve financial viability in the current economic system (along with several other things).

Electronics are integral to contemporary existence in most of the world.

Without full control over their tools, human beings cannot be free/autonomous.

Re:Sorry everybody, I failed with you by johnnyanmac on Monday June 07, 2021 @07:28PM (#27428707)
>Without full control over their tools, human beings cannot be free/autonomous.

this assumes humans want to be free/autonomous. modern society already hunts and provides power/water/shelter to most of the middle class and above populace. How many truly want that full control over their resources to begin with?

Re:Sorry everybody, I failed with you by apocalypstyx on Monday June 07, 2021 @08:12PM (#27429043)
Yes, in general humans often do everything they can to escape from freedom. Or, as the serpent said to Eve: "Here's Looking at You, Kid."
Re:Sorry everybody, I failed with you by johnnyanmac on Tuesday June 08, 2021 @12:55PM (#27437703)
you force goodwill onto humans and you push them to the serpent even faster. The whole topic here is based on making people do more work for less rewards, after all. More work billionaires benefit most from.
Re:Sorry everybody, I failed with you by rodgerd on Tuesday June 08, 2021 @12:16AM (#27430587)
To double-down on that, rms noted that he doesn't think that developers "should be able to eat sushi every day".

Which is both pretty rich coming from a guy who lived for free at a university while enjoying a million dollar grant but, more importantly, suggests that the view of the FSF on how a programmer should live, and the view of how programmers think they should live don't have a lot of overlap.

Re:Sorry everybody, I failed with you by jags on Monday June 07, 2021 @05:29PM (#27427255)
I like this idea! Free for small and paid for medium/big. I think the real wisdom lies in taking the middle path (mostly). I recently read how babel, a project used by millions, struggled to keep few full-time developers. It was heart-breaking. Great developers gets glued to the idea of open-for-all at the cost of practicality. It's kind of like how people say "follow your passion" but realistically this approach only works for a a very tiny percentage and rest just struggle to pay their bills. But I am sure some projects out there must have taken this middle path. It would be interesting to know how it worked out for them.
Re:Sorry everybody, I failed with you by galimaufry on Monday June 07, 2021 @05:23PM (#27427153)
GPL is also a possible alternative. Big companies pay you back by contributing to the project, insofar as it is worth it to them to maintain a fork and add features for their own use.
Re:Sorry everybody, I failed with you by phh on Monday June 07, 2021 @05:54PM (#27427584)
Sadly, GPL doesn't give you that. It only gives users the modified source code. No history, no time of fork. And nothing to the developer.

I think it might be time to upgrade GPL to the age of modern internet, and have licenses requiring that modification are actually PR-ed (or sent by mail or whatever) to the author.

Hell I'd even think that there could be licenses where you are required to use mainline for anything remotely looking like production, and you are not allowed to fork, you're only allowed to use as-is, and to contribute. This one would definitely not be considered FLOSS, but some components really would benefit from not having an infinite number of forks, like the Linux kernel.

Re:Sorry everybody, I failed with you by ludamad on Monday June 07, 2021 @05:46PM (#27427484)
This unfortunately worked much better before it was feasible to hide everything behind a server, having no releases so to speak at all
Re:Sorry everybody, I failed with you by zacmps on Monday June 07, 2021 @06:00PM (#27427674)
Is this not the purpose of AGPL?
Re:Sorry everybody, I failed with you by rodgerd on Tuesday June 08, 2021 @12:09AM (#27430554)
The purpose of AGPL is to have a bunch of people harass you about you daring to have the temerity of not letting them run their business on your code for free.
Re:Sorry everybody, I failed with you by WesolyKubeczek on Tuesday June 08, 2021 @03:06AM (#27431446)
But isn’t it cathartic when you tell those people to fuck off?
Re:Sorry everybody, I failed with you by zxzax on Monday June 07, 2021 @12:28PM (#27424438)
I've never liked that approach, it's leading with the stick and not the carrot and IMO it defeats the purpose of open source. It cuts away one of the main benefits of open source -- that companies can use it and start contributing back to it right away with no friction. AFAIK Microsoft, Amazon and Google actually DO hire a lot of open source maintainers at this time, for exactly this reason.
Re:Sorry everybody, I failed with you by cnml123 on Monday June 07, 2021 @12:40PM (#27424662)
Companies rarely contribute back except for very few projects like gcc and LLVM.

FAANG does hire OSS devs, but a lot of them don't really do that much apart from being excellent politicians. To be fair, they don't get any time for OSS development in the first place.

However, they do have time for politics and often ruin the projects. People play along because they want to get hired at GNAAF.

As a result, these projects combine the worst of corporate and OSS development (horrible atmosphere and yet no money for development).

Re:Sorry everybody, I failed with you by zksmk on Monday June 07, 2021 @01:43PM (#27425565)
A bit off topic, but instead of FAANG (Facebook, Apple, Amazon, Netflix, Google) I much more prefer the MAAAF or FAAAM acronym (Facebook, Apple, Alphabet, Amazon, Microsoft) because their monopolies basically make them a mafia family, and I don't really see Netflix belonging in the group.
Re:Sorry everybody, I failed with you by rkntt on Monday June 07, 2021 @02:24PM (#27426151)
That's a good point, also Netflix rarely has bad press as far as I know.

MAAAF for Mafia of MAGAF (Make Google Great Again, F...) are nicer.

Re:Sorry everybody, I failed with you by dane-pgp on Monday June 07, 2021 @05:16PM (#27427047)
If you want to make the allusion to the Mafia more obvious, then Apple could be abbreviated "i" (as in iOS, iPhone, iPad, etc.).
Re:Sorry everybody, I failed with you by dabockster on Monday June 07, 2021 @02:38PM (#27426325)
Not just politics, but often they'll couple OSS to their own build systems and stuff. Yeah, it might be 50ms faster on paper, but that whole project now depends on that company's OSS licensing allowing that dependency to exist publicly. That's some really scary power.
Re:Sorry everybody, I failed with you by zxzax on Monday June 07, 2021 @03:36PM (#27426653)
That seems to be a mostly orthogonal concern -- you're talking about a general issue of "doing business with big corporations" and not really something I would say is specific to any given project. One way to help improve the situation would be to help them win those battles so they can negotiate for more time to upstream useful things.
Re:Sorry everybody, I failed with you by spion on Monday June 07, 2021 @12:42PM (#27424694)
The problem isn't the software but the discussion around it. With discussions, issues, feature requests etc you can be a contributor or you can be a user (beneficiary). There should be a possibility to distinguish between both and require compensation from beneficiaries.

We already do this to an extent but the mechanisms are not strict enough. The stake on the ground needs to be put much earlier on, for much less demand than it typically is.

Re:Sorry everybody, I failed with you by mixedCase on Monday June 07, 2021 @04:45PM (#27426777)
"Sharing stuff you want to share with other people is for suckers"

Ok man. I mean, I'm quite capitalist myself but I draw the line before "don't share things with everyone because sharing free things like that is for suckers/commies/whatever".

If you don't like doing open source, don't do open source. There was never a requirement for you to do open source.

Doing open source doesn't mean tending to other people's feature request, or even looking at pull requests. It's just releasing code under a certain list of licenses. Which you can do, if you want to, or don't. If you want to discriminate between your users, you do you, that's not open source but unless you run afoul of the law you can go and do that.

Re:Sorry everybody, I failed with you by ItsMonkk on Monday June 07, 2021 @01:45PM (#27425600)
pg has a good article on doing things that don't scale[0] and showed how the AirBnB guys went and setup the first listings manually, but it's actually far more general than just kicking off the network effect. Moats are things that don't scale. Open Source software scales perfectly. Billion dollar companies are billion dollar companies because they can use Open Source software wrapped around some Moat-able structure. The more Open Source Software that exists, the bigger the garden.

When Google spends a billion dollars sending cars all around the world taking pictures, they are doing so in a way that the Open Source world can't centrally compete against, as they don't have the billions to get that done. This means that all Open Source mapping software will be missing a crucial feature that users rely on, and will therefore go unused. But meanwhile the libraries that those Open Source Software use, Google can freely use within their walled garden. On the other hand, Microsoft paid a great deal of money to researchers with Encarta and had this same exact structure and Wikipedia came in and disrupted them. It takes more time for the decentralized approach to come online, but as long as it's possible and the data is kept high quality Google Maps will slowly lose market share to OSM.

So eventually decentralized open source software will catch up and these billion dollar companies will go to 0, but in the interim period, and as innovation never truly ends so there is always a new horizon, we should consider creating a better incentive structure.

The big problem with capitalism today is that we care very deeply about prices. Prices is where supply and demand match, but we no longer have any supplies. We have costs of 0 and values that can differ between people. Price is merely a negotiation between the two, with Open Source Software declaring 0% of the value, and Billion Dollar companies declaring 90% of the value. Price has become a flawed metric. What society truly cares about is the surplus. What we need is a way to do a sort of Incentive Compability system[1](i.e. a Vickrey Auction) so that these Open Source Software can show the value that they produce. If they can show that their development costs were offset by their users values, they should be funded for it. Linux would certainly have a much higher value than Microsoft in this view, and would therefore be able to fund their own data collection systems, and would likely leave those open to the world so that everyone could reuse the Linux Street Map data for themselves.

[0]:http://paulgraham.com/ds.html

[1]:https://en.wikipedia.org/wiki/Incentive_compatibility

Re:Sorry everybody, I failed with you by gowld on Tuesday June 08, 2021 @10:25AM (#27435603)
> Much as I dislike those wacky "free for non-commercial use, otherwise, give me a call" licenses,

Why? Disliking someone not giving you free money seems rude.

Re:Sorry everybody, I failed with you by The_rationalist on Monday June 07, 2021 @11:00AM (#27423367)
Well your comment is meaningful but you could still have recorded the total number of downloads and the monthly number in order to answer how popular is the library.