> Try using "Emacs" or even "free software" to mean something different, and see just how quickly you would hear back from Richard Stallman. What would Stallma

> Try using "Emacs" or even "free software" to mean something different, and see just how quickly you would hear back from Richard Stallman. What would Stallman do is not the rubric I use for, well, anything really... But I can see how somebody who feels that way would be willing to cease to provide free labor because they believe they have lost control of something on account of it becoming too popular for them to maintain fiat authority over its use. Fights between individual contributors can be so strange. I find that they frequently don't actually address the underlying issue because the underlying issue can be arbitrary and somewhat petty, and engineers don't want to think of themselves as either of those things. I once got into a long argument about folder nesting depth with a co-worker only to finally discover that the underlying issue was that I was using vs code (which tacitly penalizes you the way the UI works for shallow nesting) And he was using vim (and his configuration worked better if all of the relevant files were at the same level in the file system). Once I realized the issue, I deferred to him on seniority and went about retooling my process to match to the existing process. But it took us a while to realize that was the underlying issue!