logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

The-wrong-words-but-the-right-ideas.md (5091B)


  1. ---
  2. date: 2019-09-17
  3. layout: post
  4. title: Don't sacrifice the right ideas to win the right words
  5. tags: [philosophy]
  6. ---
  7. There is a difference between free software and open-source software. But you
  8. have to squint to see it. Software licenses which qualify for one title but not
  9. the other are exceptionally rare.
  10. A fascination with linguistics is common among hackers, and I encourage and
  11. participate in language hacking myself. Unfortunately, that seems to seep into
  12. the Free Software Foundation's message a bit too much. Let's see if any of this
  13. rings familiar:
  14. > It's not actually open source, but free software. You see, "open source" is a
  15. > plot by the commercial software industry to subvert the "free software"
  16. > movement...
  17. > No, it's free-as-in-freedom, not free-as-in-beer. Sometimes we call it "libre"
  18. > software, borrowing the French or Spanish word, because in English...
  19. > What you're referring to as Linux, is in fact, GNU/Linux, or as I've recently
  20. > taken to calling it, GNU plus Linux. Linux is not an operating system...
  21. What do all of these have in common? The audience already agrees with the
  22. speaker on the ideas, but this becomes less so with every word. This kind of
  23. pedantry lacks tact and pushes people away from the movement. No one wants to
  24. talk to someone who corrects them like this, so people shut down and stop
  25. listening. The speaker gains the self-satisfaction that comes with demonstrating
  26. that you're smarter than someone else, but the cost is pushing that person away
  27. from the very ideals you're trying to clarify. This approach doesn't help the
  28. movement, it's just being a dick.
  29. For this reason, even though I fully understand the difference between free and
  30. open-source software, I use the terms basically interchangeably. In practice
  31. they are effectively the same thing. Then, I preach the ideologies behind free
  32. software even when discussing open-source software. The ideas are what matters,
  33. the goal is to get people thinking on your wavelength. If they hang around long
  34. enough, they'll start using your words, too. That's how language works.
  35. The crucial distinction of the free software movement is less about "free
  36. software", after all, and more about copyleft. But, because the FSF pushes
  37. copyleft *and* free software, and because many FSF advocates are pedantic and
  38. abrasive, many people check out before they're told the distinction between free
  39. software and copyleft. This leads to the listener *equivocating* free software
  40. with copyleft software, which undermines the message and hurts both.[^1]
  41. [^1]: For those unaware, copyleft is any "viral" license, where using copyleft code requires also using a copyleft license for your derived work. Free software is just software which meets the [free software definition][fsd], which is in practice just about all free *and* open-source software, including MIT or BSD licensed works.
  42. [fsd]: https://www.gnu.org/philosophy/free-sw.html
  43. This lack of tact is why I find it difficult to accept the FSF as a
  44. representative of the movement I devote myself to. If your goal is to strengthen
  45. the resolve and unity of people who already agree with you by appealing to
  46. tribalism, then this approach is effective - but remember that it strengthens
  47. the opposing tribes, too. If your goal is to grow the movement and win the
  48. hearts and minds of the people, then you need to use more tact in your language.
  49. Turn that hacker knack for linguistic hacking towards *this* goal, of thinking
  50. over how your phrasing and language makes different listeners feel. The
  51. resulting literature will be much more effective.
  52. Attack the systems and individuals who brought about the circumstances that
  53. frustrate your movement, but don't attack their victims. It's not the user's
  54. fault that they were raised on proprietary software. The system which installed
  55. proprietary software on their school computers is the one to blame. Our goals
  56. should be things like introducing Linux to the classroom, petitioning our
  57. governments to require taxpayer-funded software to be open source, eliminating
  58. Digital Restrictions Management[^2], pushing for right to repair, and so on. Why
  59. is "get everyone to say 'libre' instead of 'open-source'" one of our goals
  60. instead?
  61. [^2]: This kind of pedantry, which deliberately misrepresents the acronym (which is rightly meant to be "Digital Rights Management"), is more productive, since the people insulted by it are not the victims of DRM, but the perpetrators of it. Also, "Digital Rights Management" is itself a euphemism, or perhaps more accurately a kind of doublespeak, which invites a similar response.
  62. An aside: sometimes language *is* important. When someone has the wrong words
  63. but the right ideas, it's not a big deal. When someone has the wrong *ideas* and
  64. is appropriating the words to support them, that's a problem. This is why I
  65. still come down hard on companies which gaslight users with faux-open software
  66. licenses like the Commons Clause or the debacle with RedisLabs.
  67. *Note: this article is not about Richard Stallman. I have no comment on the
  68. recent controversies.*