3 ms·
I'd certainly be interested in hearing the story behind that. Personally, I have no use for Clojure, myself, and, thus, no opinions on the project, or its part
by ChrisMarshallNY 4y ago
I'd certainly be interested in hearing the story behind that.
Personally, I have no use for Clojure, myself, and, thus, no opinions on the project, or its participants; other than to sincerely wish them well, and success in their endeavors.
Because Clojure (as a specific project) is not something that I use, my opinion of the tool has no bearing on whether or not it is a good tool, or on its creators/community. I completely recognize and accept that my opinion of the tool and its creators is absolutely worthless.
So, I'm best off, keeping my mouth shut on the tool and its creators. I can live with that.
Since this was linked on the front page of HN, and seems to have remained up for four years, I can comment on what it says, in a very limited fashion, as there are a couple of things that resonate with me.
In my case, I'm the original author of a fairly important infrastructure tool, that has been completely taken over, and is being maintained, by a new team of highly capable individuals. I'm barely even a footnote on the project, and that suits me just fine. I pop into the Facebook group for the project, from time to time, and spew up a little historical anecdote, as a trivia exercise.
But I started writing that project in 2008, and released it in 2009. I then had to shepherd, maintain, evangelize, and defend the project for ten years, in a sizable community of, for lack of a better word, trolls. The project was meant to help them, and Serve their needs. Getting them to accept and embrace the tool was ... challenging. I was met with suspicion, hostility, entitled demands, condescension, hostile takeover attempts, insults, attacks of various types, etc.
Ahhh ... fun times.
But in the end, it worked out.
One of the reasons that I have all but walked away from the tool, is that ten years of keeping the pot boiling was exhausting. A lot of other stuff didn't get done, while I was working on that, and I had to hold myself back, in many ways. I also made a number of interpersonal mistakes, while evangelizing/defending the project, and learned some harsh, humbling, lessons about myself, and about others.
I am eternally grateful to the team that took the project over. I am sure that it is not their idea of a "perfect tool," but it gave them an excellent baseline, and they have extended it, far beyond my initial vision. It now Serves thousands and thousands of people daily. I was also able to soak up a lot of the bullets for them. I'm a pretty tough old coot, and knew what I was signing up for (I am intimately familiar with the target demographic). Now that it's an established project, and some of the new team are quite respected in the community, it is being treated well.
All that, to say, that I was tempted to write a manifesto like this, numerous times, but decided that it would only make things worse.
I think, in my case, that was a good decision.