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

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194
  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` element
  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,initial-scale=1">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Maybe the Book Doesn’t Need to Be “Disrupted” in the First Place? (archive) — David Larlet</title>
  13. <meta name="description" content="Publication mise en cache pour en conserver une trace.">
  14. <!-- That good ol' feed, subscribe :). -->
  15. <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
  16. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  17. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
  18. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
  19. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
  20. <link rel="manifest" href="/static/david/icons2/site.webmanifest">
  21. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
  22. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
  23. <meta name="msapplication-TileColor" content="#f7f7f7">
  24. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
  25. <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
  26. <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
  27. <!-- Is that even respected? Retrospectively? What a shAItshow…
  28. https://neil-clarke.com/block-the-bots-that-feed-ai-models-by-scraping-your-website/ -->
  29. <meta name="robots" content="noai, noimageai">
  30. <!-- Documented, feel free to shoot an email. -->
  31. <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
  32. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  33. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  34. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  35. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  36. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  37. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  38. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  39. <script>
  40. function toggleTheme(themeName) {
  41. document.documentElement.classList.toggle(
  42. 'forced-dark',
  43. themeName === 'dark'
  44. )
  45. document.documentElement.classList.toggle(
  46. 'forced-light',
  47. themeName === 'light'
  48. )
  49. }
  50. const selectedTheme = localStorage.getItem('theme')
  51. if (selectedTheme !== 'undefined') {
  52. toggleTheme(selectedTheme)
  53. }
  54. </script>
  55. <meta name="robots" content="noindex, nofollow">
  56. <meta content="origin-when-cross-origin" name="referrer">
  57. <!-- Canonical URL for SEO purposes -->
  58. <link rel="canonical" href="https://countercraft.substack.com/p/maybe-the-book-doesnt-need-to-disrupted">
  59. <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">
  60. <article>
  61. <header>
  62. <h1>Maybe the Book Doesn’t Need to Be “Disrupted” in the First Place?</h1>
  63. </header>
  64. <nav>
  65. <p class="center">
  66. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  67. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  68. </svg> Accueil</a> •
  69. <a href="https://countercraft.substack.com/p/maybe-the-book-doesnt-need-to-disrupted" title="Lien vers le contenu original">Source originale</a>
  70. </p>
  71. </nav>
  72. <hr>
  73. <p><span>A dozen years ago, I was out of grad school and desperate for a job. (Ideally one I could slack off in while I wrote my novel.) I ended up in the offices of a tech startup that had big plans to use the emerging tech of ebooks to innovate, amplify, revolutionize, and fundamentally disrupt the entire concept of books! The exact name of the company doesn’t matter. There were plenty of them. “Enhanced ebooks” were </span><a href="https://www.nytimes.com/2010/07/29/books/29ebook.html" rel>buzzed about in every newspaper</a><span> and VCs were tossing millions at anyone who could put “gamify” and “publish” in the same sentence. The future was here, and these radical techno-books would make Gutenberg look like a troglodyte. </span></p>
  74. <p><em>How</em><span> would books be revolutionized? That was less clear. Mostly the plan seemed to be adding pop-up videos and images to ebook files. You could be reading </span><em>The Great Gatsby</em><span> and click on the sentence “a single green light, minute and far away, that might have been the end of a dock” and see what a green light looks like I guess. </span></p>
  75. <div class="captioned-image-container"><figure><a class="image-link image2" target="_blank" href="https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F888189d8-3b38-45d4-8027-5d7e70e2175b_298x222.png" rel></a><figcaption class="image-caption">A green light, possibly at the end of a dock</figcaption></figure></div>
  76. <p>It seemed silly to me. Beyond a few specific types of books—a high school history textbook, say—few people are looking to have their reading experience constantly interrupted by pop-up videos. It’s distracting enough reading with cellphone text notifications going off. The last thing I want reading a novel is to pause mid-chapter and watch a video clip. </p>
  77. <p>Perhaps my face showed my skepticism. I didn’t get the job. But 12 years later—a lifetime in tech—and the book is in more or less the shame shape it was 12 years ago or 120 years ago. “Enhanced ebooks” went nowhere. Ebooks themselves certainly exist, but despite all the hype about new fancy features most ebook readers—themselves a minority of book buyers—want their digital books to resemble printed books about as closely as possible. </p>
  78. <p>In the intervening years, I’ve seen countless versions of enhanced books hyped. Last year, there were articles about how “web 3” and crypto would completely change publishing by [something something string of jargon] block chain! All the magazines publishing daily articles on Web 3 and NFTs have stopped talking about them, seemingly in embarrassment as the crypto space has been exposed as a series of Ponzi schemes. (The crypto crowd is too busy focusing on “disrupting” the legal system to keep themselves out of jail to innovate the novel, I guess.) So naturally everyone who, last year, was declaring crypto would revolutionize every aspect of life have pivoted to saying “A.I.” will revolutionize every aspect of life. And, like the tweet above, that means lots of predictions about how the book will be disrupted. (Commenters to the above tweet also suggested putting books in the “metaverse” so you can “live” books instead of read them, whatever that means…) </p>
  79. <p>I’m on the record as a bit of an “A.I” skeptic. And I’m putting A.I. in scare quotes because a computer program that spits out text it doesn’t understand is not an “intelligence” really. (Renaming “software” as “A.I.” was a very clever marketing coup. People freak out when they hear an “A.I.” did something like win a spelling bee even though no one would be terribly impressed to hear a computer program with a built-in dictionary did that.) Still, I think what we’re calling A.I. will have significantly more impact on certain parts of our life than “enhanced ebooks.” Some predictions here: </p>
  80. <p>Anyway, the fact that “A.I.” writing programs might have some uses (good and bad) doesn’t mean books will fundamentally change. The reason that all of these predictions for the disruption of the book have gone nowhere isn’t that the tech doesn’t work—well sometimes that’s the case—but because the book maybe just doesn’t need disruption. </p>
  81. <p><span>Reading is a technology that works. And it works in part by immersing the reader in the text itself. The lack of video / music / pop-up ads / crypto tokens / mini-games aren’t a problem to be solve. The lack of those thing is the feature. Books are engaging precisely </span><em>because</em><span> they lack those things. </span></p>
  82. <p><span>Then again it’s unclear to me what these tech-brain people actually mean, if anything, when they talk about disrupting books with gamification / enhancements / blockchain / VR / the metaverse / NFTs / or any other buzzword. I’ve never seen anyone explain their vision of this jargon that didn’t sound like they just wanted books to </span><em>be </em><span>video games or movies. </span></p>
  83. <p>These mediums have their different purposes and we tend to want to use them separately. When you watch a movie, you want to watch a movie. When you read a book, you want to read a book. Few people want to play videogames where the action is interrupted by 30 pages of text or a half-hour cutscene. By the same token, few people want to read a novel and have the chapters interrupted by streaming videos or “gamified” functions. </p>
  84. <p><span>One of the mistakes the tech stan makes is assuming </span><em>more </em><span>is always an improvement. That we always want more features, more apps, more enhancements. But when you have a well-functioning technology, often what you want is </span><em>less</em><span>. The reason that ebooks have stuck around isn’t because they have </span><em>more </em><span>features than books, it’s because they are simpler in certain contexts. I use ebooks primarily when I’m traveling, because an ebook reader weighs far less than a stack of books, or when I’m reading an unpublished manuscript from a friend or student, because it’s a pain to get printed and I want to </span><em>avoid </em><span>all the “features” of a laptop when reading. </span></p>
  85. <p><span>Of course, I realize some people will read this newsletter and say I’m a “Luddite” or “dinosaur.” (Silly, perhaps, to say to </span><a href="https://www.amazon.com/Body-Scout-Novel-Lincoln-Michel/dp/0316628727" rel>a science fiction writer</a><span> who writes and thinks about the possibilities of new technology.) I was called those names when, a decade ago, I wrote articles saying that while ebooks would be a real thing it was unlikely they’d replace printed books in the way digital music replaced CDs. But the fact is the tech skeptics get it right at least as often as the tech optimists. Remember, the people telling you Web 3 or blockchain are about to usher in a revolution of all human life are the same ones tossing millions of dollars at Theranos and </span><a href="https://www.theguardian.com/technology/2017/sep/01/juicero-silicon-valley-shutting-down" rel>Juicero</a><span>. </span></p>
  86. <div class="captioned-image-container"><figure><a class="image-link is-viewable-img image2" target="_blank" href="https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2e95bac7-5a08-4f4f-a232-a863a8cf700d_757x452.png" rel></a><figcaption class="image-caption">120 million dollars in VC funding for… a machine that squeezes a bag of juice</figcaption></figure></div>
  87. <p><span>But even framing these questions as “optimist” vs. “skeptic” is off. Often technology doesn’t fail or take over. Much of the time technology works fine, but just doesn’t </span><em>replace</em><span> something else that also works fine. </span></p>
  88. <p><span>Recently I saw </span><em>Avatar 2</em><span> in theaters because, well, why not? At some point during the 3+ hour long film, I thought, huh, I don’t think I’ve seen a single movie in 3D since I saw the last Avatar movie 13 years ago. Weren’t 3D movies supposed to become the default movie experience? At least until holographic movies and VR movies and AR movies overtook them? </span></p>
  89. <p><span>Despite all the hype when </span><em>Avatar </em><span>came out in 2009, 3D movies have never come close to replacing 2D screenings. Considering how much movie watching has moved to the home, especially since the pandemic, the percentage of movies watched in 3D is quite small. 3D films, like ebooks, aren’t failed technology. They function and enjoy a decent chunk of the marketplace. They have features that regular movies and regular books don’t… and yet most people most of the time prefer the “dinosaur” versions. </span></p>
  90. <p>I guess what I’m saying is, the book is still a pretty good piece of tech all these centuries later. They’re plenty engaging without gadgets, features, and blockchains. Hell, maybe I’ll log off and read one now. </p>
  91. <p><hr></p>
  92. <p><em>If you want to read some of my thoughts about the future in book form, check out my science fiction novel </em><a href="https://bookshop.org/books/the-body-scout/9780316628723" rel>The Body Scout</a><em>, which </em><span>The New York Times</span><em> called “Timeless and original” and </em><span>Esquire </span><em>listed as one of the “50 Best Sci-Fi Books of All Time.”</em></p>
  93. </article>
  94. <hr>
  95. <footer>
  96. <p>
  97. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  98. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  99. </svg> Accueil</a> •
  100. <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
  101. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-rss2"></use>
  102. </svg> Suivre</a> •
  103. <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
  104. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-user-tie"></use>
  105. </svg> Pro</a> •
  106. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
  107. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-mail"></use>
  108. </svg> Email</a> •
  109. <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
  110. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-hammer2"></use>
  111. </svg> Légal</abbr>
  112. </p>
  113. <template id="theme-selector">
  114. <form>
  115. <fieldset>
  116. <legend><svg class="icon icon-brightness-contrast">
  117. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-brightness-contrast"></use>
  118. </svg> Thème</legend>
  119. <label>
  120. <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
  121. </label>
  122. <label>
  123. <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
  124. </label>
  125. <label>
  126. <input type="radio" value="light" name="chosen-color-scheme"> Clair
  127. </label>
  128. </fieldset>
  129. </form>
  130. </template>
  131. </footer>
  132. <script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
  133. <script>
  134. function loadThemeForm(templateName) {
  135. const themeSelectorTemplate = document.querySelector(templateName)
  136. const form = themeSelectorTemplate.content.firstElementChild
  137. themeSelectorTemplate.replaceWith(form)
  138. form.addEventListener('change', (e) => {
  139. const chosenColorScheme = e.target.value
  140. localStorage.setItem('theme', chosenColorScheme)
  141. toggleTheme(chosenColorScheme)
  142. })
  143. const selectedTheme = localStorage.getItem('theme')
  144. if (selectedTheme && selectedTheme !== 'undefined') {
  145. form.querySelector(`[value="${selectedTheme}"]`).checked = true
  146. }
  147. }
  148. const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
  149. window.addEventListener('load', () => {
  150. let hasDarkRules = false
  151. for (const styleSheet of Array.from(document.styleSheets)) {
  152. let mediaRules = []
  153. for (const cssRule of styleSheet.cssRules) {
  154. if (cssRule.type !== CSSRule.MEDIA_RULE) {
  155. continue
  156. }
  157. // WARNING: Safari does not have/supports `conditionText`.
  158. if (cssRule.conditionText) {
  159. if (cssRule.conditionText !== prefersColorSchemeDark) {
  160. continue
  161. }
  162. } else {
  163. if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
  164. continue
  165. }
  166. }
  167. mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
  168. }
  169. // WARNING: do not try to insert a Rule to a styleSheet you are
  170. // currently iterating on, otherwise the browser will be stuck
  171. // in a infinite loop…
  172. for (const mediaRule of mediaRules) {
  173. styleSheet.insertRule(mediaRule.cssText)
  174. hasDarkRules = true
  175. }
  176. }
  177. if (hasDarkRules) {
  178. loadThemeForm('#theme-selector')
  179. }
  180. })
  181. </script>
  182. </body>
  183. </html>