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 37KB

  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 don’t you go live in a cave?” - when technophiles cry troglodyte (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/05/18/why-dont-you-go-live-in-a-cave-when-technophiles-cry-troglodyte/">
  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 don’t you go live in a cave?” - when technophiles cry troglodyte (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/05/18/why-dont-you-go-live-in-a-cave-when-technophiles-cry-troglodyte/">Source originale du contenu</a></h3>
  445. <blockquote><p>Someone<br/>
  446. came to the stones<br/>
  447. and said:<br/>
  448. Be human</p>
  449. <p>The stones<br/>
  450. replied:<br/>
  451. We are not<br/>
  452. hard enough<br/>
  453. yet</p>
  454. <p>– Erich Fried<a href="#_edn1" name="_ednref1">[i]</a></p></blockquote>
  455. <p> </p>
  456. <p><strong>1)</strong></p>
  457. <p>Regardless of where arguments about the impact of technology on society begin, these disagreements have a tendency to end at the entrance to a cave. Indeed, amongst a certain subset of individuals who periodically engage with this subject matter, a cave represents the only possible conclusion for a certain line of criticism. The group of discussants may have been pleasantly, or heatedly, quibbling over the merits and drawbacks of particular technologies but eventually the person taking the role of technology’s defender (and/or celebrant) has simply had enough. They throw up their hands in frustration, and declare “if you really think that technology is so bad, why don’t you go live in a cave,” or the slightly cleverer version of this sentiment, “if people did what you said we’d still be living in caves.”</p>
  458. <p>The cave represents an odd conclusion. And to be clear, it almost always is the conclusion of the discussion. For the individual who brings up the cave deploys it as a sort of ultimate trump card, a magnificent argument winning move from which the other person cannot possibly recover. While for the individual against whom the cave card is played (this usually being the person in the argument who was putting forth a critical analysis of technology), the use of the cave demonstrates that there is no point continuing the conversation as the other person is clearly not debating in good faith. Ultimately, evoking the cave says much more about the worldview of the person who brings up the cave, than the worldview of the person against whom the cave is deployed. It represents a cluster of logical fallacies nicely lathered with a thick coat of technofideism and passed off as a serious intervention insofar as it is a view that is largely in line with dominant narratives around technological progress and inevitability.</p>
  459. <p>It may well be that “go live in a cave” is just a particularly persnickety version of the <a href="https://librarianshipwreck.wordpress.com/2017/07/20/against-the-anti-technology-strawman/">“anti-technology strawman”</a> (perhaps it should be called the “anti-technology caveman”). Nevertheless, given the frequency with which this particular argument pops up it seems deserving of more direct attention.</p>
  460. <p> </p>
  461. <p><strong>2)</strong></p>
  462. <p>Though the cave may appear to have a solid earth-bound foundation it sits atop fairly rocky premises. It represents a straw man argument, a reduction to absurdity, as well as a slippery slope – all moves that weaken the argument more than assisting it.</p>
  463. <p>The cave is a strawman argument insofar as it creates a caricature of critiques of technology, and creates a caricature of the particular critic with whom the person deploying the cave is arguing. The cave simultaneously represents a comic oversimplification and a gross exaggeration of criticism of technology. It plays upon the imprecise way in which people frequently talk about technology in order to suggest that criticisms of particular technologies in particular contexts are actually criticisms of all technology in all contexts. And following from this the cave latches onto the critic’s suggestion that “maybe the world would be better off without a particular technology,” in order to suggest that what is actually being suggested is that the world would be better off without <em>any</em> and <em>all</em> technology. In trying to attribute to critics of technology a totalizing analysis that cannot differentiate between a technology and all technology, the person who brings up the cave discards the nuances of their opponent’s argument. And thus, the person who voices some opposition towards particular instantiations of a large class of things (and technology is certainly a large class of things) is treated as though they oppose the entire class, as such. Far from knocking the stuffing out of the actual critique put forth in terms of criticism of technology, this strawman attempts to paint any (and every) critic as desperate to drag humanity back to the stone age. When, in actuality, these critics don’t want to go back to the stone age (or even a few decades ago) – they simply want to raise concerns about where it seems we’re going.</p>
  464. <p>The cave represents an absurd destination, albeit one which is framed as the inevitable goal for criticism of technology. It is an argument that takes any criticism and leaps with it in a ludicrous direction. Those who criticize Facebook and Google aren’t saying that they want to, or that they want everybody to, go live in the wilderness. Those who critique the way that the computer has become omnipresent in many contemporary societies aren’t saying that all computers must be destroyed. And even those who say that people should get offline periodically and go outside aren’t really saying that people must never go online again. To take any such points and say that what these people really want is for everybody to go live in caves is simply silly. Yet it builds off a fear that what starts as a critique of Facebook will eventually turn into a critique of the Internet which will eventually turn into a critique of computers which will eventually turn into a critique of electricity which will eventually…lead to a demand that people go live in caves. This is the view that any critique of technology sends us racing down this perilous slippery slope that has the stone age at its bottom. Therefore, the logic of the cave argument runs: one shouldn’t criticize technology at all, because if those arguments are allowed we’ll wind up huddled around the fire for warmth as sabre toothed tigers growl from the shadows. True, critiques of one technology may lead to critiques of other technologies, but to suggest that this inevitably ends with the idea that humanity should go back to living in caves is nonsense.</p>
  465. <p>Rather than honestly engage with criticisms of technology, the cave switches the playing field into a farcical sphere. In fairness, the cave works by forcing critics of technology onto the defensive as they are compelled to voice things such as, “I’m not saying that I want us to go back to living in caves,” whereas they had never been saying that in the first place. Thus, the cave performs a pithy bait and switch whereby the person who was doing the criticizing is placed on the defensive while the person who was doing the defending is now placed on the offensive – it means that the person who brings up the cave no longer has to defend their claims about technology, they can instead force the critic of technology to profess that they were not voicing an opinion which they were never actually professing.</p>
  466. <p>Yet, the fallacious structure of the cave retort suggests a deeper truth than simply a failure to actually engage. Rather, the cave demonstrates a mode of thinking in which there are only two alternatives: unfettered high-tech society or the stone age.</p>
  467. <p> </p>
  468. <p><strong>3)</strong></p>
  469. <p>While the cave argument does not deserve to be taken seriously as an actual argument, if one wants to approach those making the argument with a touch of good faith it may be worth considering where this argument comes from. At its base, it seems that the argument is a knee-jerk reaction derived from the aforementioned dichotomy wherein the choice is either high-tech everything or the stone age. However, if one wants to be generous to those making the cave argument, one can recognize that the cave argument (though hyperbolic) is not too distant from less ridiculous retorts that are leveled at those who critique technology. And, perhaps, by redirecting the cave argument towards less absurd grounds – a conversation can continue (though this assumes, probably overly optimistically, that the cave argument is being made in good faith).</p>
  470. <p>The cave represents the extreme exaggeration of an accusation that has been leveled, with some reason, at many critics of technology, namely: romanticism. This accusation – which was particularly popular as a retort against nineteenth and twentieth-century critics – captured the sense that many critics seemed to have a clear preference for a way of life prior to the rise of industrialization. To suggest that a particular critic was guilty of romanticizing the past was an argument that transcended national boundaries or political ideologies, but what was generally shared by these “romantic critics” was a certain sense of loss entangled with the experience of modernity. And, in fairness, many critics attributed much of this loss to the way that new technologies were transforming society. Importantly, this did not mean that these critics wanted to return to the stone age – or that they wanted people to live in caves. Rather, they recognized that with the gains brought by new technologies, so too came losses.</p>
  471. <p>Furthermore, they saw that technologies were not value neutral but instead carried particular agendas for the arrangement of society. This is not to say that these individuals were resistant to change or in favor of upholding the status quo. Indeed, many of them were active social reformers, utopian thinkers, and revolutionaries who wanted to see the world around them changed. They were just wary of the way that new technologies were changing their worlds, and they foresaw that the impacts of these machines would be deleterious to living beings. This is a matter that has been explored at length in works such as <a href="https://librarianshipwreck.wordpress.com/2016/12/22/my-favorite-books-from-2016/">Rosalind Williams’s <em>The Triumph of Human Empire</em></a>, in <em>Romanticism Against the Tide of Modernity </em>by Michael Löwy and Robert Sayre, and can be detected by actually taking the time to go back and read the writings of these thinkers.</p>
  472. <p>Thus, there may be some truth to the argument that some critics of technology (and social critics in general) have had a tendency to look to the past. And, in many of these cases this looking backwards is burnished by a certain fondness for trees. Yet the problem emerges if one believes that these thinkers sought to genuinely return to the past. Rather, the point of looking backwards was not to return to the past, but to learn from it, and carry useful lessons from it into the present and the future. After all, if you want to understand how technology is changing society it helps to have a more complex knowledge of history than one that boils down to just saying “things used to be bad, and now they’re better.” Indeed, one of the areas that many of the critics who are accused of romanticism (wrongly or rightly) focused on was the moments in the past when alternative paths could have been taken.</p>
  473. <p>Nevertheless, to highlight the point that must be emphasized: these thinkers did not want to go back to the stone age. They wanted everyone to go forward into a golden age, and they feared that the technology they criticized was not genuinely taking people towards such a brighter age. And though they may have had trepidations about the future, they were not endorsing a static existence in the status quo. Rather, as Ivan Illich, a critic whose analyses certainly earned him all manner of cave like reprimands, put it: “I’m not endorsing the past. It’s <em>past</em>, it’s <em>gone</em>. Even less am I endorsing the present. I’m subject to it, I’m in it.”<a href="#_edn2" name="_ednref2">[ii]</a> One need not want to return to the past, or be satisfied with the present, to be anxious about the future.</p>
  474. <p>There are certainly criticisms that can, and should, be directed at critics of technology and critics of society. After all, it is through such critiquing of critiques that these views can become sharpened. But the only thing that saying “so-and-so would have us go live in caves” demonstrates is that one has not actually read “so-and-so.”</p>
  475. <p> </p>
  476. <p><strong>4)</strong></p>
  477. <p>Granted, there may be another area from whence those who make the cave argument try to base their barb. And this may have less to do with the accusation of “romanticism” (mainly a nineteenth century accusation) and more to do with the epithet “prophet of doom” (more generally used in the twentieth and twenty-first century). After all, many critics of technology did have a habit of talking about going back to the stone age, with much of humanity having to seek shelter in caves; however, they were not saying this as a suggestion of what to do, but as a warning of things to come.</p>
  478. <p>For many social critics, certain technologies represented dire threats to human civilization’s future. In the twentieth-century, many a critic was highly concerned with the threat that nuclear weapons posed to the world. In the writings of a range of thinkers one encounters dire predictions about what the world would look like after a nuclear war – and in many of these cases, the thinker imagined a world in which the disaster wound up setting the clock back to the stone age. Importantly, none of these arguments were based on a sentiment that it would be good to go back to the stone age. When they envisioned humanity hiding out in caves to escape the blighted nuclear deathscape that much of the world might become, or humanity living underground in massive bunker civilizations, they were not arguing in favor of these things. Rather they were using the specter of the stone age and the cave as a warning against the types of apocalyptic threats that technological advances were making possible. Thus, their suggestion that “technological society is going to lead us back to the stone age” was not an endorsement of the stone age, but a grim prediction that humanity had advanced tremendously in technological ways – but not nearly as much in terms of the moral advancement necessary to control those technological advancements. Many of these critics were also concerned about the nascent development of “the computer dominated society” (as <a href="https://librarianshipwreck.wordpress.com/2014/10/19/the-good-life-or-the-goods-life-the-thought-of-lewis-mumford/">Lewis Mumford</a> called it), but this was hardly an endorsement of the status quo, instead it was a recognition that things don’t always change for the better. It’s not that they preferred the cave over the computer, but that they thought that computers were creating a society of “mass-produced hermits” (to use Günther Anders formulation) who were so isolated from one another that they might as well have been living in caves.</p>
  479. <p>These twentieth-century critics, with their anxiety about nuclear weapons, may appear somewhat outdated (<a href="https://librarianshipwreck.wordpress.com/2017/08/09/atomic-warfare-means-universal-extermination/">though nuclear paranoia seems, alas, to be back in vogue</a>) – but environmental concerns have been another area wherein social critics and critics of technology have highlighted that the unthinking embrace of every new technology might wind up leading to the type of catastrophe that sends us back to the stone age. <a href="https://librarianshipwreck.wordpress.com/2017/07/11/the-apocalyptic-turn/">Alas, climate change seems to have replaced nuclear war as the technologically exacerbated threat du jour</a> – but both push critics to imagine the disastrous scenarios that can potentially arise should nothing be done. As Isabelle Stengers has recently written, regarding climate change, “Over the last few years one has had to cede to the evidence: what was lived as a rather abstract possibility, the global climatic disorder, has well and truly begun.”<a href="#_edn3" name="_ednref3">[iii]</a> Pointing to the threat and openly outlining the potential risk (the collapse of civilization as we know it), is not advocating for a return to the stone age. Quite the contrary, it is suggesting that the adoration for all things high-tech (common amongst those who deploy the cave argument), risks sending us back to the stone age. This is not an argument for a return to the past, but an argument based on building a better future. And it is from this perspective that many of the most radical environmental critiques should be read: de-growth, turning things off, leveling, moving away from a consumer lifestyle – can be read as being not so much “good” in and of themselves, but as ways to avoid societal collapse. And those “radical” steps are not simply the hobbyhorse of anarcho-primitivists, they make up much of the argument of <a href="https://librarianshipwreck.wordpress.com/2015/06/24/laudato-si/">Pope Francis’s encyclical <em>Laudato Si</em>.</a></p>
  480. <p>All of which is to say, those who use the “return to caves” argument as an attack are cleverly mobilizing it against their opponents as a way of distracting from the fact that what many of their opponents are really saying isn’t that we should go back to living in caves. But that, at the rate we’re going, our unthinking embrace of every new high-tech gadget is going to wind up leading us back to the stone age.</p>
  481. <p> </p>
  482. <p><strong>5)</strong></p>
  483. <p>The past, the present, and the future are about alternatives. When we look at the past, we can see not only what happened, but different paths that could have been taken. When we look at the present, we see similar things, not only how things are happening but how they could be happening differently. And when we look at the future, we can see a host of alternative scenarios, though a consideration of the past and the present helps us to predict which of those scenarios is most likely to unfold. An awareness of the range of possibilities is key, and thus one of the most damaging aspects of the cave argument is not that it is silly, not that it is hyperbolic, and not that it is made in bad faith – but that it limits our ability to imagine the future. For what the “return to caves” argument, at base, accomplishes is to limit future possibilities to two equally unacceptable alternatives: either we accept every new high-tech gadget and giant corporation <a href="https://librarianshipwreck.wordpress.com/2017/03/31/when-real-life-emulates-dystopia-it-isnt-a-good-sign/">no matter how dystopian</a> and no matter how evocative of Black Mirror…or we return to living in caves.</p>
  484. <p>This is a farcical choice based on a ridiculous dichotomy, that ultimately serves to disempower and depoliticize individuals. It is centered on an ahistorical understanding of technology that portrays technology as inevitable and erases the role that people play in guiding these decisions. As the computer scientist, AI pioneer, and social critic <a href="https://librarianshipwreck.wordpress.com/2016/07/27/an-island-of-reason-in-the-cyberstream-on-the-life-and-thought-of-joseph-weizenbaum/">Joseph Weizenbaum</a> wisely observed: “The myth of technological and political and social inevitability is a powerful tranquilizer of the conscience. Its serve is to remove responsibility from the shoulders of everyone who truly believes in it. But, in fact, there <em>are</em> actors!”<a href="#_edn4" name="_ednref4">[iv]</a></p>
  485. <p>And that is precisely what “the return to caves” argument in all of its fallacious silliness achieves: it is a “tranquilizer of the conscience” that allows technological evangelists to refuse to think through the implications of technology by casting those who insist on thinking through such implications as troglodytes. It treats as inevitable those things which history reveals to be anything but inevitable. What is needed now is to think through, and work to create, the types of alternatives that the “return to caves” argument overlooks – steps that will counter the “tranquilizer of the conscience” with a reenergizing of the conscience. We all lose when the only choice afforded to us is between passively accepting a high-tech cyberpunk world ruled by massive corporations, and a return to the stone age.</p>
  486. <p>Ours is a moment when we desperately need to be having serious discussions about technology and society, and we should recognize that the “return to caves” argument is an attempt to shut that conversation down.</p>
  487. </article>
  488. </section>
  489. <nav id="jumpto">
  490. <p>
  491. <a href="/david/blog/">Accueil du blog</a> |
  492. <a href="https://librarianshipwreck.wordpress.com/2018/05/18/why-dont-you-go-live-in-a-cave-when-technophiles-cry-troglodyte/">Source originale</a> |
  493. <a href="/david/stream/2019/">Accueil du flux</a>
  494. </p>
  495. </nav>
  496. <footer>
  497. <div>
  498. <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
  499. <p>
  500. Bonjour/Hi!
  501. 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>
  502. 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>).
  503. </p>
  504. <p>
  505. 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>.
  506. </p>
  507. <p>
  508. Voici quelques articles choisis :
  509. <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
  510. <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
  511. <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
  512. <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
  513. <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
  514. <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
  515. <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
  516. <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
  517. <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
  518. <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
  519. <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
  520. <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
  521. <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
  522. <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
  523. <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
  524. et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
  525. </p>
  526. <p>
  527. 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>.
  528. </p>
  529. <p>
  530. Je ne traque pas ta navigation mais mon
  531. <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
  532. conserve des logs d’accès.
  533. </p>
  534. </div>
  535. </footer>
  536. <script type="text/javascript">
  537. ;(_ => {
  538. const jumper = document.getElementById('jumper')
  539. jumper.addEventListener('click', e => {
  540. e.preventDefault()
  541. const anchor = e.target.getAttribute('href')
  542. const targetEl = document.getElementById(anchor.substring(1))
  543. targetEl.scrollIntoView({behavior: 'smooth'})
  544. })
  545. })()
  546. </script>