Burnout Is Real in the OSS World, Says John-David Dalton, Creator of Lodash
49 points
1 hour ago
| 6 comments
| openjsf.org
| HN
FinnLobsien
38 minutes ago
[-]
If you have a hobby project like writing a blog, crocheting, or almost any other creative hobby, you can dip in and out however it suits you. If you deal with major life events, sicknesses, etc., you can leave the hobby and come back. Nobody is paying you for it, so nobody can complain (maybe the friends who miss you, but it's not actively impacting the real world).

Open source is one of those weird things where your hobby project can become an essential piece of infrastructure.

It's like if you loved crocheting, but somehow if you stopped crocheting everyone in your city would no longer have clothes and need to walk around naked.

reply
subygan
14 minutes ago
[-]
and nobody is willing to pay for it.
reply
FinnLobsien
4 minutes ago
[-]
The value created vs value captured equation of OSS must be one of the most lopsided things ever.

If you’re at Google and invent Kubernetes you might still capture 0.000001% (probably less) of the economic value created by Kubernetes, but you probably enjoy very generous comp.

OSS doesn’t have any of that, besides being extremely in demand as a consultant or whatever.

reply
asim
46 minutes ago
[-]
I wrote recently about bringing back my open source project back from the dead. It's more than a decade old. Many life events occured during that time. It's tough. It's nothing like Lodash but honestly these things ebb and flow. It operates in cycles just as life does. Wish him all the best. Sounds like he had many tough years personally and I can relate.

https://go-micro.dev/blog/27

reply
reactordev
23 minutes ago
[-]
There’s only so many sprints you can do back to back to back… you are correct, things ebb and flow and they’ll relax and life will happen and they’ll come back and either pick it up or start a new. It’s OK. It’s all OK.
reply
dheera
3 minutes ago
[-]
I had an open source project (https://github.com/dheera/rosboard) that I burned out and didn't really do a good job continue maintaining.

* I was burned out from work politics at the same time, and had to prioritize fighting those work politics since that's what was paying me. By the end of each day at that company, I didn't feel like staring at a screen any more

* I would get a flurry of poorly-tested pull requests that would break it for some users

* I got lots of suggestions of <feature to implement> which weren't well thought out for how to generalize

* No actually good engineer stepped up to say "I want to help with this"

* There was a commercial alternative that had gotten funding and they were better at marketing

reply
bstsb
37 minutes ago
[-]
> This conversation was initially just a phone call, but was so powerful that we decided to turn it into a blog and share the audio via YouTube

i can tell - it looks like the blog post doesn't really add anything over a direct transcript of the call itself. it's just a bland summary of the really interesting story Dalton told

reply
cronelius
10 minutes ago
[-]
So does this mean no Lodash 5?
reply
Devasta
43 minutes ago
[-]
This is unironically why the AGPL3 is the best license. No need to worry about "virality" or derivative works or any of that, just set it and forget it. On top of that, corporations will avoid you like the plague, ensuring that your audience is other AGPL3 users.
reply
embedding-shape
22 minutes ago
[-]
I've used MIT almost exclusively for anything I've published, under multiple identities, and seems to work fine too. What benefit would AGPL3 give me over MIT, in terms of avoiding burnout? So far, saying "No" or not working for free for companies, been working fine as an approach so far, but always open to hearing even better approaches.
reply
hilariously
2 minutes ago
[-]
It prevents the No from ever materializing because almost no one wants to use your code to build on top of.
reply
arikrahman
40 minutes ago
[-]
I am happy with the network solution AGPL provides on top of GPL. I think a new AGPL version needs to come out that addresses rewriting codebases with AI and claiming new original work.
reply
FinnLobsien
36 minutes ago
[-]
How would you enforce that? I'm genuinely curious. It's nearly impossible to conclusively prove someone rewrote your codebase with AI.
reply
Raed667
32 minutes ago
[-]
Unless they proudly claim it as they seem so keen to do
reply