Bozhidar Batsov

I really like the author's response after he closed the request and people kept commenting on it. > Disclaimer: I'm starting to write this at 7 am in my morning, so my thoughts are a bit incoherent. > I wonder how all of you would feel if suddenly a ton of people who haven't done anything for the project appeared here, told you're a horrible person and started bullying you into doing what they want... > For almost a decade I've been doing pro-bono work on the style guides, RuboCop and many related projects, but all of this gets easily forgotten. You come out of nowhere, you vilify me over this, you fork the project without even discussing this idea with our team... Whatever. The US has many issues, but so does the open-source community. If even I wanted to rename the project we're talking about 300+ extensions, usages in tens of thousands of projects, messing up with search results that have been building up for years, etc, and an insane amount of work associated with this. I've made nothing out of RuboCop and now you're adding a huge pile of disappointment and frustration on top of this nothing. > This feels like a great opportunity to double down on the Ruby community ethos and get a ton of positive publicity by rebranding. At the same time, let's recognise that the request implies a bunch of time and even some material expense for @bbatsov (registered domain names, doc sites etc. beyond "just" renaming in code), and some help scoping that out would probably be…

Somebody brought up a point about outdated documentation. Currently https://clojuredocs.org is sort of the go to place. It wins due to Google algorithm. I wanted to add the ability to vote on answers provided there. So that you have the ability to see the most relevant/popular answer, rather than the oldest. Raised an issue on the repo, four years ago now. No response: https://github.com/zk/clojuredocs/issues/222 And why do I mention Google algorithm? Because there was another effort that tried to create a (debatably) nicer documentation, but due to lack of Google traffic, it died. See: https://news.ycombinator.com/item?id=8027119 For a more eloquent argument on its uses, see this blog post: https://metaredux.com/posts/2019/06/29/farewell-grimoire.html

Here is the recap of someone is interested https://metaredux.com/posts/2023/09/09/clojure-support-in-emacs-one-un…

Other examples: - "master"/"slave" terminology in databases and such; most recently, even the "master" branch in source trees was deemed impious, and GitHub will be renaming it by default to "main" on new repos starting tomorrow - there was a recent case where the author of RuboCop (a linter for Ruby, a pun on RoboCop) faced a lot of pressure to rename it because, I guess, cops are now considered verboten (!?): https://metaredux.com/posts/2020/06/08/the-rubocop-name-drama-redux.ht… - adding codes of conduct to all public-facing projects, most of which are taken directly from the Contributor Covenant (a safely orthodox choice); this isn't a naming thing, but is pushed for in a similar way by similar people

Here's a link to a blog post detailing the thinking of Bozhidar Batsov, RuboCop's author: https://metaredux.com/posts/2020/06/08/the-rubocop-name-drama-redux.ht…

I hope... this is not another feature that is added to Ruby at the sake of the functional programming trend. Rubycop’s author criticized[0] Ruby 2.7 for losing a direction/vision where Ruby should go (which sparked controversial operators that were quickly removed). Most of them looks like, at least to me, trying to fit a functional programming features in an inherently object-oriented language to be ‘hip’. Like... the pipeline operator which had strange semantics. I hope this isn’t one. [0] Ruby, Where do We Go Now?: https://metaredux.com/posts/2019/12/06/ruby-where-do-we-go-now.html