A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

index.html 35KB

4 lat temu
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang=fr>
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset=utf-8>
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name=viewport content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Why the Luddites Matter (archive) — David Larlet</title>
  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
  17. <link rel="manifest" href="/manifest.json">
  18. <link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
  19. <link rel="shortcut icon" href="/static/david/icons/favicon.ico">
  20. <meta name="apple-mobile-web-app-title" content="David Larlet">
  21. <meta name="application-name" content="David Larlet">
  22. <meta name="msapplication-TileColor" content="#da532c">
  23. <meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
  24. <meta name="theme-color" content="#f0f0ea">
  25. <!-- That good ol' feed, subscribe :p. -->
  26. <link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">
  27. <meta name="robots" content="noindex, nofollow">
  28. <meta content="origin-when-cross-origin" name="referrer">
  29. <!-- Canonical URL for SEO purposes -->
  30. <link rel="canonical" href="https://librarianshipwreck.wordpress.com/2018/01/18/why-the-luddites-matter/">
  31. <style>
  32. /* http://meyerweb.com/eric/tools/css/reset/ */
  33. html, body, div, span,
  34. h1, h2, h3, h4, h5, h6, p, blockquote, pre,
  35. a, abbr, address, big, cite, code,
  36. del, dfn, em, img, ins,
  37. small, strike, strong, tt, var,
  38. dl, dt, dd, ol, ul, li,
  39. fieldset, form, label, legend,
  40. table, caption, tbody, tfoot, thead, tr, th, td,
  41. article, aside, canvas, details, embed,
  42. figure, figcaption, footer, header, hgroup,
  43. menu, nav, output, ruby, section, summary,
  44. time, mark, audio, video {
  45. margin: 0;
  46. padding: 0;
  47. border: 0;
  48. font-size: 100%;
  49. font: inherit;
  50. vertical-align: baseline;
  51. }
  52. /* HTML5 display-role reset for older browsers */
  53. article, aside, details, figcaption, figure,
  54. footer, header, hgroup, menu, nav, section { display: block; }
  55. body { line-height: 1; }
  56. blockquote, q { quotes: none; }
  57. blockquote:before, blockquote:after,
  58. q:before, q:after {
  59. content: '';
  60. content: none;
  61. }
  62. table {
  63. border-collapse: collapse;
  64. border-spacing: 0;
  65. }
  66. /* http://practicaltypography.com/equity.html */
  67. /* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
  68. /* https://www.filamentgroup.com/lab/js-web-fonts.html */
  69. @font-face {
  70. font-family: 'EquityTextB';
  71. src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
  72. url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  73. font-weight: 300;
  74. font-style: normal;
  75. font-display: swap;
  76. }
  77. @font-face {
  78. font-family: 'EquityTextB';
  79. src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
  80. url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  81. font-weight: 300;
  82. font-style: italic;
  83. font-display: swap;
  84. }
  85. @font-face {
  86. font-family: 'EquityTextB';
  87. src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
  88. url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  89. font-weight: 700;
  90. font-style: normal;
  91. font-display: swap;
  92. }
  93. @font-face {
  94. font-family: 'ConcourseT3';
  95. src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
  96. url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  97. font-weight: 300;
  98. font-style: normal;
  99. font-display: swap;
  100. }
  101. /* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
  102. body {
  103. /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  104. font-family: "EquityTextB", Palatino, serif;
  105. background-color: #f0f0ea;
  106. color: #07486c;
  107. font-kerning: normal;
  108. -moz-osx-font-smoothing: grayscale;
  109. -webkit-font-smoothing: subpixel-antialiased;
  110. text-rendering: optimizeLegibility;
  111. font-variant-ligatures: common-ligatures contextual;
  112. font-feature-settings: "kern", "liga", "clig", "calt";
  113. }
  114. pre, code, kbd, samp, var, tt {
  115. font-family: 'TriplicateT4c', monospace;
  116. }
  117. em {
  118. font-style: italic;
  119. color: #323a45;
  120. }
  121. strong {
  122. font-weight: bold;
  123. color: black;
  124. }
  125. nav {
  126. background-color: #323a45;
  127. color: #f0f0ea;
  128. display: flex;
  129. justify-content: space-around;
  130. padding: 1rem .5rem;
  131. }
  132. nav:last-child {
  133. border-bottom: 1vh solid #2d7474;
  134. }
  135. nav a {
  136. color: #f0f0ea;
  137. }
  138. nav abbr {
  139. border-bottom: 1px dotted white;
  140. }
  141. h1 {
  142. border-top: 1vh solid #2d7474;
  143. border-bottom: .2vh dotted #2d7474;
  144. background-color: #e3e1e1;
  145. color: #323a45;
  146. text-align: center;
  147. padding: 5rem 0 4rem 0;
  148. width: 100%;
  149. font-family: 'ConcourseT3';
  150. display: flex;
  151. flex-direction: column;
  152. }
  153. h1.single {
  154. padding-bottom: 10rem;
  155. }
  156. h1 span {
  157. position: absolute;
  158. top: 1vh;
  159. left: 20%;
  160. line-height: 0;
  161. }
  162. h1 span a {
  163. line-height: 1.7;
  164. padding: 1rem 1.2rem .6rem 1.2rem;
  165. border-radius: 0 0 6% 6%;
  166. background: #2d7474;
  167. font-size: 1.3rem;
  168. color: white;
  169. text-decoration: none;
  170. }
  171. h2 {
  172. margin: 4rem 0 1rem;
  173. border-top: .2vh solid #2d7474;
  174. padding-top: 1vh;
  175. }
  176. h3 {
  177. text-align: center;
  178. margin: 3rem 0 .75em;
  179. }
  180. hr {
  181. height: .4rem;
  182. width: .4rem;
  183. border-radius: .4rem;
  184. background: #07486c;
  185. margin: 2.5rem auto;
  186. }
  187. time {
  188. display: bloc;
  189. margin-left: 0 !important;
  190. }
  191. ul, ol {
  192. margin: 2rem;
  193. }
  194. ul {
  195. list-style-type: square;
  196. }
  197. a {
  198. text-decoration-skip-ink: auto;
  199. text-decoration-thickness: 0.05em;
  200. text-underline-offset: 0.09em;
  201. }
  202. article {
  203. max-width: 50rem;
  204. display: flex;
  205. flex-direction: column;
  206. margin: 2rem auto;
  207. }
  208. article.single {
  209. border-top: .2vh dotted #2d7474;
  210. margin: -6rem auto 1rem auto;
  211. background: #f0f0ea;
  212. padding: 2rem;
  213. }
  214. article p:last-child {
  215. margin-bottom: 1rem;
  216. }
  217. p {
  218. padding: 0 .5rem;
  219. margin-left: 3rem;
  220. }
  221. p + p,
  222. figure + p {
  223. margin-top: 2rem;
  224. }
  225. blockquote {
  226. background-color: #e3e1e1;
  227. border-left: .5vw solid #2d7474;
  228. display: flex;
  229. flex-direction: column;
  230. align-items: center;
  231. padding: 1rem;
  232. margin: 1.5rem;
  233. }
  234. blockquote cite {
  235. font-style: italic;
  236. }
  237. blockquote p {
  238. margin-left: 0;
  239. }
  240. figure {
  241. border-top: .2vh solid #2d7474;
  242. background-color: #e3e1e1;
  243. text-align: center;
  244. padding: 1.5rem 0;
  245. margin: 1rem 0 0;
  246. font-size: 1.5rem;
  247. width: 100%;
  248. }
  249. figure img {
  250. max-width: 250px;
  251. max-height: 250px;
  252. border: .5vw solid #323a45;
  253. padding: 1px;
  254. }
  255. figcaption {
  256. padding: 1rem;
  257. line-height: 1.4;
  258. }
  259. aside {
  260. display: flex;
  261. flex-direction: column;
  262. background-color: #e3e1e1;
  263. padding: 1rem 0;
  264. border-bottom: .2vh solid #07486c;
  265. }
  266. aside p {
  267. max-width: 50rem;
  268. margin: 0 auto;
  269. }
  270. /* https://fvsch.com/code/css-locks/ */
  271. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  272. font-size: 1rem;
  273. line-height: calc( 1.5em + 0.2 * 1rem );
  274. }
  275. h1 {
  276. font-size: 1.9rem;
  277. line-height: calc( 1.2em + 0.2 * 1rem );
  278. }
  279. h2 {
  280. font-size: 1.6rem;
  281. line-height: calc( 1.3em + 0.2 * 1rem );
  282. }
  283. h3 {
  284. font-size: 1.35rem;
  285. line-height: calc( 1.4em + 0.2 * 1rem );
  286. }
  287. @media (min-width: 20em) {
  288. /* The (100vw - 20rem) / (50 - 20) part
  289. resolves to 0-1rem, depending on the
  290. viewport width (between 20em and 50em). */
  291. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  292. font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
  293. line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
  294. margin-left: 0;
  295. }
  296. h1 {
  297. font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  298. line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  299. }
  300. h2 {
  301. font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  302. line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  303. }
  304. h3 {
  305. font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  306. line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  307. }
  308. }
  309. @media (min-width: 50em) {
  310. /* The right part of the addition *must* be a
  311. rem value. In this example we *could* change
  312. the whole declaration to font-size:2.5rem,
  313. but if our baseline value was not expressed
  314. in rem we would have to use calc. */
  315. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  316. font-size: calc( 1rem + .6 * 1rem );
  317. line-height: 1.5em;
  318. }
  319. p, li, pre, details {
  320. margin-left: 3rem;
  321. }
  322. h1 {
  323. font-size: calc( 1.9rem + 1.5 * 1rem );
  324. line-height: 1.2em;
  325. }
  326. h2 {
  327. font-size: calc( 1.5rem + 1.5 * 1rem );
  328. line-height: 1.3em;
  329. }
  330. h3 {
  331. font-size: calc( 1.35rem + 1.5 * 1rem );
  332. line-height: 1.4em;
  333. }
  334. figure img {
  335. max-width: 500px;
  336. max-height: 500px;
  337. }
  338. }
  339. figure.unsquared {
  340. margin-bottom: 1.5rem;
  341. }
  342. figure.unsquared img {
  343. height: inherit;
  344. }
  345. @media print {
  346. body { font-size: 100%; }
  347. a:after { content: " (" attr(href) ")"; }
  348. a, a:link, a:visited, a:after {
  349. text-decoration: underline;
  350. text-shadow: none !important;
  351. background-image: none !important;
  352. background: white;
  353. color: black;
  354. }
  355. abbr[title] { border-bottom: 0; }
  356. abbr[title]:after { content: " (" attr(title) ")"; }
  357. img { page-break-inside: avoid; }
  358. @page { margin: 2cm .5cm; }
  359. h1, h2, h3 { page-break-after: avoid; }
  360. p3 { orphans: 3; widows: 3; }
  361. img {
  362. max-width: 250px !important;
  363. max-height: 250px !important;
  364. }
  365. nav, aside { display: none; }
  366. }
  367. ul.with_columns {
  368. column-count: 1;
  369. }
  370. @media (min-width: 20em) {
  371. ul.with_columns {
  372. column-count: 2;
  373. }
  374. }
  375. @media (min-width: 50em) {
  376. ul.with_columns {
  377. column-count: 3;
  378. }
  379. }
  380. ul.with_two_columns {
  381. column-count: 1;
  382. }
  383. @media (min-width: 20em) {
  384. ul.with_two_columns {
  385. column-count: 1;
  386. }
  387. }
  388. @media (min-width: 50em) {
  389. ul.with_two_columns {
  390. column-count: 2;
  391. }
  392. }
  393. .gallery {
  394. display: flex;
  395. flex-wrap: wrap;
  396. justify-content: space-around;
  397. }
  398. .gallery figure img {
  399. margin-left: 1rem;
  400. margin-right: 1rem;
  401. }
  402. .gallery figure figcaption {
  403. font-family: 'ConcourseT3'
  404. }
  405. footer {
  406. font-family: 'ConcourseT3';
  407. display: flex;
  408. flex-direction: column;
  409. border-top: 3px solid white;
  410. padding: 4rem 0;
  411. background-color: #07486c;
  412. color: white;
  413. }
  414. footer > * {
  415. max-width: 50rem;
  416. margin: 0 auto;
  417. }
  418. footer a {
  419. color: #f1c40f;
  420. }
  421. footer .avatar {
  422. width: 200px;
  423. height: 200px;
  424. border-radius: 50%;
  425. float: left;
  426. -webkit-shape-outside: circle();
  427. shape-outside: circle();
  428. margin-right: 2rem;
  429. padding: 2px 5px 5px 2px;
  430. background: white;
  431. border-left: 1px solid #f1c40f;
  432. border-top: 1px solid #f1c40f;
  433. border-right: 5px solid #f1c40f;
  434. border-bottom: 5px solid #f1c40f;
  435. }
  436. </style>
  437. <h1>
  438. <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  439. Why the Luddites Matter (archive)
  440. <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
  441. </h1>
  442. <section>
  443. <article>
  444. <h3><a href="https://librarianshipwreck.wordpress.com/2018/01/18/why-the-luddites-matter/">Source originale du contenu</a></h3>
  445. <blockquote><p>Chant no more your old rhymes about bold Robin Hood,</p>
  446. <p>His feats I but little admire</p>
  447. <p>I will sing the achievements of General Ludd</p>
  448. <p>Now the Hero of Nottinghamshire</p>
  449. <p><em>– General Ludd’s Triumph, </em><a href="#_edn1" name="_ednref1">[1]</a></p></blockquote>
  450. <p>Colloquialisms have a remarkable way of convincing their users that they have done their homework. All that is needed is a spoonful of vaguely historically adjacent meaning to be stirred in with the waters of repeat usage, and suddenly a speaker feels confident that they understand the capital “t” truth behind a term or idea. After all, the thinking goes, if this usage of this term isn’t historically accurate, then why has this term become used in this way? Why indeed. But if you are going to use a term because of the evocative historic meaning you think is bound up in it, you probably want to make sure that you’re getting your history right.</p>
  451. <p>Which brings us to the Luddites.</p>
  452. <p>It is undeniable that the term Luddite has become fairly common shorthand in much of the English speaking world. As it is commonly deployed in regular discourse the term has come to be an easy descriptor for someone who “hates technology,” someone who is “afraid of technology,” or someone who is simply “bad with technology.” Depending on its specific usage, Luddite is can either be used as an expression of comical self-deprecation, or it is thrown about as an insult. Lurking somewhere in the background of most people’s usage of the term is just enough historical knowledge to get partial credit on a history test: the Luddites were some people long ago in England who smashed some machines. Onto this basic foundation, other things wind up getting thrown in as well: the Luddites hated technology, the Luddites hated progress, if the Luddites won we’d be living in caves, the Luddites were illiterate idiots, and so forth. As the historian E.P. Thompson aptly observed before laying waste to the historical basis of this belief, “Luddism lingers in the popular mind as an uncouth, spontaneous affair of illiterate handworkers, blindly resisting machinery.”<a href="#_edn2" name="_ednref2">[2]</a> For a society awash in smartphones, in love with the Internet, and with its hopes for a better future pinned on Silicon Valley – the Luddites appear as the perfect bogeymen. The specter of the Luddites makes it easy to disparage anyone who dares speak out against anything technological by painting them as fools pining for the past who really just want everyone to go live in caves in the woods.</p>
  453. <p>Of course, much of this popular imaginary of the historic Luddites is dead wrong. When the term Luddite is swung about carelessly it smashes any sense of historical nuance, and supplants contemporary values and ideologies for those actually held by the Luddites. Used as a colloquial epithet, Luddite is a powerful method for cutting off critical thinking.</p>
  454. <p>Yet, to put it directly, why does it matter how we talk about the Luddites?</p>
  455. <p>Because when we talk about the Luddites, we aren’t talking about the real Luddites, we’re talking about ourselves. And so we should be very careful about the values that are being snuck into the way we talk.</p>
  456. <p>So, who were the real Luddites?</p>
  457. <p>The historic Luddites were skilled craft workers laboring in England in the early 19th century, and they were amongst the first groups to see their jobs and lifestyles fall victim to mechanization; their opposition to “obnoxious” machinery was in keeping with their view that the imposition of these machines would bring “a sad end to an honourable craft.”<a href="#_edn3" name="_ednref3">[3]</a> The turn to machine-breaking, the tactic for which they are remembered, was not a “spontaneous affair” but came only after the workers appeals to parliament to protect their “honourable craft” were ignored.<a href="#_edn4" name="_ednref4">[4]</a> The Luddites took up arms but they did so with support of their communities,<a href="#_edn5" name="_ednref5">[5]</a> and they rose up out of a sense that they were protecting rights that had been established by “Custom and Law.”<a href="#_edn6" name="_ednref6">[6]</a> The actions of the Luddites took on a variety of forms, not solely limited to machine-breaking, that are best captured by Eric Hobsbawm’s description of them as: “collective bargaining by riot.”<a href="#_edn7" name="_ednref7">[7]</a> The assaults on machines were not simply about “blindly resisting machinery,” rather the Luddites chose the sites of their ire based on how the new machines were being set to action in those particular factories. The Luddites picked their targets carefully as they waged their campaign, the frames they targeted for breaking were those that belonged to employers who had used these new machines as an excuse to lower worker’s wages,<a href="#_edn8" name="_ednref8">[8]</a> and this was a trend seen across the areas where the Luddites rose .<a href="#_edn9" name="_ednref9">[9]</a></p>
  458. <p>Eventually the Luddites were suppressed, violently at that. Soldiers were deployed to quell the unrest, and parliament made machine breaking punishable by death. Yet, it would be unwise to suggest that the Luddites actions met with no success. By the time that Luddism died down the actions of this “army of redressers” had succeeded in convincing many of the factory owners to pay better wages; and the end of Luddism was not the result of the rising’s failure but due to the number of soldiers that had been mobilized to quash it and by the threat of the new legislation.<a href="#_edn10" name="_ednref10">[10]</a> Importantly, this did not mark the end of machine breaking as a tactic, far from it. <a href="https://librarianshipwreck.wordpress.com/2014/08/28/who-was-captain-swing/">From the latter part of 1830 into 1831, England was once more convulsed by machine-breaking in the form of The Swing Riots.</a><a href="#_edn11" name="_ednref11">[11]</a> In the course of which, displaced workers attacked threshing machines, in what Eric Hobsbawm and George Rudé called the “Luddism of the poor.”<a href="#_edn12" name="_ednref12">[12]</a> And though this movement was eventually repressed as well, it was both more destructive of machinery and more successful for those who participated, which prompted Hobsbawm and Rudé to observe that “the real name of King Ludd was Swing.”<a href="#_edn13" name="_ednref13">[13]</a></p>
  459. <p>One cannot fully encapsulate all of a complex history in two paragraphs – but what the above summary hopefully demonstrates is a few pertinent details regarding the Luddites that run counter to what most people think when they hear that term thrown around. First, the Luddites did not indiscriminately attack “all machines,” but directed their outrage at certain machines, in certain factories, being used in certain ways. Second, the Luddites were a popular movement in their time and their end came not due to “inevitable technological progress” but due to the deployment of soldiers and the introduction of harsh legislation. Third, the tactic of “machine breaking” though it is often associated with the Luddites is not exclusive to them: history is filled with examples of workers purposely breaking their machines as a way of resisting not against machinery (as such) but the broader economic system. Lastly, and perhaps most importantly is that which is bound up in Hobsbawm’s evocative phrase “collective bargaining by riot” a term that suggests that the best way to think of the Luddites is as forerunners of the labor movement; as workers they had no protections (a point confirmed for them when parliament refused to protect their craft) and so they quite literally took matters into their own hands.</p>
  460. <p>As for the question of what the Luddites wanted, or what the world would look like if the Luddites had been able to “have their way”? Frankly, the Luddites wanted to be able to feed their children, they didn’t want to be driven into poverty, and they thought those things were more important than the factory owners becoming wealthier and more powerful. There is nothing particularly radical or incomprehensible about such desires. You probably want to be able to feed your children (if you have any), you probably don’t want to be driven into poverty, and you probably feel that your economic security is at least as important as your boss’s ability to buy a new vacation home. Had the Luddites had “their way” they would have been given a voice in determining their labor conditions, and they would have been allowed to share in the benefits of the new machinery. It’s ridiculous to suggest they were opposed to “progress” because the ideologies hung on that term today were unknown in that time; but if we must keep with the language of “progress” it’s not that the Luddites opposed it, they just thought they should get to benefit as well. As the historian David Noble commented, “the Luddites were perhaps the last people in the West to perceive technology in the present tense and to act upon that perception.”<a href="#_edn14" name="_ednref14">[14]</a> That which makes the Luddites so strange, so radical, and so dangerous is not that they wanted everyone to go back to living in caves (they didn’t want that), but that they thought that those who would be impacted by a new technology deserved a voice in how it was being deployed.</p>
  461. <p>Of course, we know that today the Luddites are not viewed particularly kindly. And the “why” of this brings us back to an earlier point: when we talk about the Luddites, we aren’t talking about the real Luddites, we’re talking about ourselves. Or, as Theodor Roszack once put it: “if the Luddites had never existed, their critics would have to invent them.”<a href="#_edn15" name="_ednref15">[15]</a></p>
  462. <p>The contemporary moment is one in which technological tales dominate many headlines: delivery drones, thinner smartphones, wearable gadgets, driverless cars, robots, big data, bitcoin, social media, nuclear weapons, hacking, virtual reality…and the list could go on. And behind those tales stand publicly praised tech moguls: Jeff Bezos, Bill Gates, Mark Zuckerberg, Elon Musk, Jeff Bezos…and the list goes on. Generally, these new technologies are framed as inevitable, these fortunes are framed as being linked to “geniuses,” furthermore the hoi polloi are told that “resistance is futile” and that all of these things represent “progress.” And you don’t want to resist progress, do you? You aren’t [gasp!] some kind of Luddite, are you?</p>
  463. <p>There is a widespread belief in contemporary computer dominated societies, that regular people are not allowed any say in the discussions around the types of technologies that radically reshape their lives. And the way that the term Luddite is commonly used functions to reify this belief by making people believe that they cannot push back against technology. Of course, as the above history demonstrated, the irony is that what the Luddites prove is that you actually can push back, you can build up a mass movement around it, and you can in fact be so successful that the government is forced to deploy soldiers and pass harsh legislation in order to squash you.</p>
  464. <p>Need a more recent example? <a href="https://librarianshipwreck.wordpress.com/2015/01/21/on-broken-glass/">How about Google Glass</a>. When Google unveiled that wearable high-tech headset it was framed as “inevitable,” those who raised worries were dismissed as “Luddites,” and Google seemed hellbent on pushing forward regardless. Google Glass was going to be the next thing, not because regular people wanted it to be, but because Google insisted that it would be. But a funny thing happened: people said no, and Google’s “world changing” product was shelved. There’s certainly a difference between the public rejecting a piece of consumer technology and workers pushing back against mechanization – but the common thread that connects them is that you do not have to let a tech company screaming “technological progress” in your face turn you into a paragon of passivity. And what’s more you don’t have to accept a false dichotomy wherein saying no to one kind of technology means that you are rejecting all technology.</p>
  465. <p>What an honest consideration of the Luddites allows is for us to see ourselves as active forces within the technological world. We can choose what to use. We can choose what not to use. We can choose how we use things. We can unite with other people to push for certain things, to push against other things. We can reclaim our ability to recognize that technology is not a neutral force in our lives or in our society. In the midst of recent years that have shown the sorts of racist and misogynistic biases that are often endemic in the tech world, we would be well advised to accept some Luddite skepticism about the values embodied in new technologies. As the computer scientist and AI pioneer Joseph Weizenbaum wisely it: “the myth of technological and political and social inevitability is a powerful tranquilizer of the conscience. Its service is to remove responsibility from the shoulders of everyone who truly believes in it. But, in fact, there <em>are</em> actors!”<a href="#_edn16" name="_ednref16">[16]</a> The Luddites remind us that there <em>are</em> people behind these technologies, those people have their own values, those values get built into the technological systems they’re building – and those values aren’t necessarily the same as our values. Moreover, the Luddites remind us that we too <em>are</em> actors.</p>
  466. <p>Before closing it is essential to recognize a key bait and switch that is pulled when Luddite is used as an ahistorical insult: it serves to turn particular acts of resistance, against particular technologies, in particular contexts, into acts that are against all technology. It would be ridiculous to claim that a person who dislikes McDonald’s or critiques factory farming is “anti-food,” and it is just as ridiculous to claim that a person who dislikes Google or who critiques the labor practices behind high-tech gadgets is “anti-technology.” That a person opposes Google Glass doesn’t mean that they oppose eyeglasses, that a person is wary of facial recognition software doesn’t mean they oppose cameras. <a href="https://librarianshipwreck.wordpress.com/2017/07/20/against-the-anti-technology-strawman/">As it is commonly used “Luddite” is a strawman</a>, it transmutes any criticism of a certain piece of technology or a certain use of a certain piece of technology into an attack on all technology. And though this is ridiculous, it works to advance a particular set of ideological and economic values wherein the only thing that matters is “technological progress.” And what often goes unseen and unsaid is that “technological progress” is not a game in which everyone wins, oftentimes such “progress” only serves to increase the power of those who are already powerful. As Langdon Winner observed: “Current developments in the information age suggest an increase in power by those who already had a great deal of power, an enhanced centralization of control by those already prepared for control, an augmentation of wealth by the already wealthy.”<a href="#_edn17" name="_ednref17">[17]</a> At risk of being crass, the more religiously someone sings the praises of “technological progress” the further they and their family live from an e-waste dump. And of course the supreme irony of the idea that had the Luddites won we’d be “living in caves” is that what is threatening to send us back to the stone age is nuclear war (decidedly high-tech), and technologically exacerbated climate change.</p>
  467. <p>Those who bristle at the suggestion that they stop using Luddite as an epithet often say that “meanings change over time.” This is clearly true, but it’s worth considering the value systems that are behind those changes. Furthermore, it also demonstrates a discomforting level of fecklessness meshed with a stunning disregard for history. One also frequently hears people defend the use of the term by claiming “we need this term,” but in all seriousness: what “we” is being used here? Certainly, massive tech companies and the tech press want a useful strawman/bogeyman in order to convince you that the best you can be in the contemporary world is a hapless consumer. But do you really need such a term? And do you really want to defend the position that the history bound up in a term doesn’t matter if lots of people use that term?</p>
  468. <p>Admittedly, I write this as a doctoral student whose research focuses on the history of technology, and the traditions of critiques of technology. And I must report that it seems quite obvious that terms like “anti-technology” and even “technophobia” are just signs of lazy thinking, they say far more about the person using those terms than the people being accused of being “anti-technology.” In the vast majority of cases when you actually consider what these so-called “anti-technology” folks believe you realize that they don’t oppose “all” technology but (brace yourself) particular technologies, being used in particular ways, in a particular context. This is not to pretend that genuinely “extreme” cases don’t exist, but to claim that someone who thinks Facebook has become too big wants us all to go back to living in the woods is patently absurd. Yet it is the type of absurdity that becomes common in a society that has lost the ability to think critically about technology. And having the right terminology, can be an important step in renewing critical thinking. Which is why many individuals have, with unfortunately limited success, tried to rehabilitate the term Luddite. Alas, many serious thinkers remain so terrified of being tarred as Luddites that they begin their books (or articles, or talks) by carefully intoning how much they love technology – but the result of all of this is that it cedes the terms of the argument to the companies that want you to buy a new phone, want you to keep hitting like, and want you to upload a selfie to their fun new app so that you can help hone their facial recognition algorithms.</p>
  469. <p>We are in the midst of a moment in time when many people are emphasizing how important it is for people to think seriously about history. So let us think about the history of technology. And let us think about the Luddites not as caricatures, but as real people.</p>
  470. <p>The Luddites were not “anti-technology.” They were skilled craft workers who believed that the new machinery being deployed by factory owners would impoverish, disempower, and immiserate them. They were right. They didn’t want “zero technology,” they wanted to feed their families. If they had their way we wouldn’t be living in a world with “no technology,” we’d be living in a world where communities have a say in the technological decisions that will impact them.</p>
  471. <p>It is truly a shame that in 2018 many people have a less nuanced understanding of technology and progress than the Luddites had in 1812.</p>
  472. </article>
  473. </section>
  474. <nav id="jumpto">
  475. <p>
  476. <a href="/david/blog/">Accueil du blog</a> |
  477. <a href="https://librarianshipwreck.wordpress.com/2018/01/18/why-the-luddites-matter/">Source originale</a> |
  478. <a href="/david/stream/2019/">Accueil du flux</a>
  479. </p>
  480. </nav>
  481. <footer>
  482. <div>
  483. <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
  484. <p>
  485. Bonjour/Hi!
  486. Je suis <a href="/david/" title="Profil public">David&nbsp;Larlet</a>, je vis actuellement à Montréal et j’alimente cet espace depuis 15 ans. <br>
  487. Si tu as apprécié cette lecture, n’hésite pas à poursuivre ton exploration. Par exemple via les <a href="/david/blog/" title="Expériences bienveillantes">réflexions bimestrielles</a>, la <a href="/david/stream/2019/" title="Pensées (dés)articulées">veille hebdomadaire</a> ou en t’abonnant au <a href="/david/log/" title="S’abonner aux publications via RSS">flux RSS</a> (<a href="/david/blog/2019/flux-rss/" title="Tiens c’est quoi un flux RSS ?">so 2005</a>).
  488. </p>
  489. <p>
  490. Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
  491. </p>
  492. <p>
  493. Voici quelques articles choisis :
  494. <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
  495. <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
  496. <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
  497. <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
  498. <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
  499. <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
  500. <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
  501. <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
  502. <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
  503. <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
  504. <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
  505. <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
  506. <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
  507. <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
  508. <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
  509. et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
  510. </p>
  511. <p>
  512. On peut <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">échanger par courriel</a>. Si éventuellement tu souhaites que l’on travaille ensemble, tu devrais commencer par consulter le <a href="http://larlet.com">profil dédié à mon activité professionnelle</a> et/ou contacter directement <a href="http://scopyleft.fr/">scopyleft</a>, la <abbr title="Société coopérative et participative">SCOP</abbr> dont je fais partie depuis six ans. Je recommande au préalable de lire <a href="/david/blog/2018/cout-site/" title="Attention ce qui va suivre peut vous choquer">combien coûte un site</a> et pourquoi je suis plutôt favorable à une <a href="/david/pro/devis/" title="Discutons-en !">non-demande de devis</a>.
  513. </p>
  514. <p>
  515. Je ne traque pas ta navigation mais mon
  516. <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
  517. conserve des logs d’accès.
  518. </p>
  519. </div>
  520. </footer>
  521. <script type="text/javascript">
  522. ;(_ => {
  523. const jumper = document.getElementById('jumper')
  524. jumper.addEventListener('click', e => {
  525. e.preventDefault()
  526. const anchor = e.target.getAttribute('href')
  527. const targetEl = document.getElementById(anchor.substring(1))
  528. targetEl.scrollIntoView({behavior: 'smooth'})
  529. })
  530. })()
  531. </script>