Post by @MaddieM4@raphus.social

Stefano Marinelli
@stefano @bsd.cafe

Over the past few days, I've spent quite a lot of time revisiting some tools I wrote for Linux many years ago. Some of them have been running in production for well over a decade. They work well, I've kept improving them over the years, and I think they could be useful to other people too.

So I started cleaning up the comments (in Italian, mostly), reviewing a few things, thinking about making them public. And then I stopped.

I'm not sure I want to release them anymore.

It's not about the work involved. I enjoy writing things, and I enjoy sharing them. I've been doing both for almost thirty years. But lately, with some of my projects, I've found myself spending more time explaining why I chose to do things in a certain way than discussing the software itself.

Why didn't I use this? Why didn't I follow that convention? Why isn't the development history publicly visible? Why not simply do what everyone else does?

And, to be clear, I have absolutely nothing against these questions. Asking questions is perfectly legitimate. What bothers me is the assumption that, if someone does things differently, there must be something wrong with their approach. Sometimes even something suspicious.

Last Saturday, during my talk at Linux Day, I mentioned something that I consider fundamental: Open Source is about freedom. Not about replacing one set of imposed conventions with another.

Thirty years ago, people asked me why I didn't just use Windows. Today, when something doesn't compile on a BSD, someone inevitably asks why I don't just use Linux. Which is rather funny, considering that I use Linux extensively and have done so since 1996.

But that's not the point, is it?

I don't dislike conventions. I don't dislike Git, public development or any of the practices that have become common over the years. I use many of them myself. I simply don't think they should become requirements for being considered a legitimate member of the Open Source community.

I have always disliked monopolies, including monopolies of thought. And I find it rather sad to see the same pressure to conform appearing in a world that attracted me precisely because it offered an alternative.

Perhaps I'm just getting a little tired. Not of developing things, but of having to justify my choices every time they differ from what people expect.

So, for now, I think those tools will remain where they've been for all these years: running on my servers, doing their job. Maybe I'll change my mind. I hope so, actually.

But right now, I don't feel like going through all of that again.

And that's a pity, because I still believe that sharing what we create is one of the best things about Open Source.

#OpenSource #BeFree

Replying to @stefano@bsd.cafe
MaddieM4
@MaddieM4 @raphus.social

@stefano I think that's entirely valid.

These days, I put a lot of work into explaining why I do things, not really to silence critics, but because I want people to be able to easily evaluate if my software fits how someone wants their tools to work, not just "does it do a task." I also use my software as case studies of patterns I think are healthier than the mainstream, or experiments worthy of exploring.

Both of these are *also* reactions to thought monoculture as a problem. And they're a higher effort than a lot of people have the spoons to bother with, because thought monoculture is exhausting and oppressive.

Stefano Marinelli
@stefano @bsd.cafe

@MaddieM4 And I think that's an important distinction. I actually enjoy explaining why I do things differently. Sometimes the reasoning behind a particular choice is more interesting than the software itself, and discussing different approaches is one of the things I've always loved about Open Source.

What I find exhausting is having to *defend* those choices, as if doing something differently were a mistake that needs to be justified.

I'm perfectly happy when someone questions my decisions. I've learned a lot from those discussions over the years. But there's a difference between curiosity and the expectation that everyone should eventually arrive at the same conclusions.

And yes, that takes energy. Sometimes more than writing the software in the first place.