davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529
							<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang=fr>
<!-- Has to be within the first 1024 bytes, hence before the <title>
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset=utf-8>
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name=viewport content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
<!-- Required to make a valid HTML5 document. -->
<title>The billionaire’s typewriter (archive) — David Larlet</title>
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
<link rel="manifest" href="/manifest.json">
<link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
<link rel="shortcut icon" href="/static/david/icons/favicon.ico">
<meta name="apple-mobile-web-app-title" content="David Larlet">
<meta name="application-name" content="David Larlet">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
<meta name="theme-color" content="#f0f0ea">
<!-- That good ol' feed, subscribe :p. -->
<link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="http://practicaltypography.com/billionaires-typewriter.html">

<style>
/* http://meyerweb.com/eric/tools/css/reset/ */
html, body, div, span,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, address, big, cite, code,
del, dfn, em, img, ins,
small, strike, strong, tt, var,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, embed,
figure, figcaption, footer, header, hgroup,
menu, nav, output, ruby, section, summary,
time, mark, audio, video {
  margin: 0;
  padding: 0;
  border: 0;
  font-size: 100%;
  font: inherit;
  vertical-align: baseline;
}
/* HTML5 display-role reset for older browsers */
article, aside, details, figcaption, figure,
footer, header, hgroup, menu, nav, section { display: block; }
body { line-height: 1; }
blockquote, q { quotes: none; }
blockquote:before, blockquote:after,
q:before, q:after {
  content: '';
  content: none;
}
table {
  border-collapse: collapse;
  border-spacing: 0;
}

/* http://practicaltypography.com/equity.html */
/* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
/* https://www.filamentgroup.com/lab/js-web-fonts.html */
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  font-weight: 300;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  font-weight: 300;
  font-style: italic;
  font-display: swap;
}
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  font-weight: 700;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: 'ConcourseT3';
  src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
       url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  font-weight: 300;
  font-style: normal;
  font-display: swap;
}


/* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
body {
  /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  font-family: "EquityTextB", Palatino, serif;
  background-color: #f0f0ea;
  color: #07486c;
  font-kerning: normal;
  -moz-osx-font-smoothing: grayscale;
  -webkit-font-smoothing: subpixel-antialiased;
  text-rendering: optimizeLegibility;
  font-variant-ligatures: common-ligatures contextual;
  font-feature-settings: "kern", "liga", "clig", "calt";
}
pre, code, kbd, samp, var, tt {
  font-family: 'TriplicateT4c', monospace;
}
em {
  font-style: italic;
  color: #323a45;
}
strong {
  font-weight: bold;
  color: black;
}
nav {
  background-color: #323a45;
  color: #f0f0ea;
  display: flex;
  justify-content: space-around;
  padding: 1rem .5rem;
}
  nav:last-child {
    border-bottom: 1vh solid #2d7474;
  }
  nav a {
    color: #f0f0ea;
  }
  nav abbr {
    border-bottom: 1px dotted white;
  }

h1 {
  border-top: 1vh solid #2d7474;
  border-bottom: .2vh dotted #2d7474;
  background-color: #e3e1e1;
  color: #323a45;
  text-align: center;
  padding: 5rem 0 4rem 0;
  width: 100%;
  font-family: 'ConcourseT3';
  display: flex;
  flex-direction: column;
}
  h1.single {
    padding-bottom: 10rem;
  }
  h1 span {
    position: absolute;
    top: 1vh;
    left: 20%;
    line-height: 0;
  }
    h1 span a {
      line-height: 1.7;
      padding: 1rem 1.2rem .6rem 1.2rem;
      border-radius: 0 0 6% 6%;
      background: #2d7474;
      font-size: 1.3rem;
      color: white;
      text-decoration: none;
    }
h2 {
  margin: 4rem 0 1rem;
  border-top: .2vh solid #2d7474;
  padding-top: 1vh;
}
h3 {
  text-align: center;
  margin: 3rem 0 .75em;
}
hr {
  height: .4rem;
  width: .4rem;
  border-radius: .4rem;
  background: #07486c;
  margin: 2.5rem auto;
}
time {
  display: bloc;
  margin-left: 0 !important;
}
ul, ol {
  margin: 2rem;
}
ul {
  list-style-type: square;
}
a {
  text-decoration-skip-ink: auto;
  text-decoration-thickness: 0.05em;
  text-underline-offset: 0.09em;
}
article {
  max-width: 50rem;
  display: flex;
  flex-direction: column;
  margin: 2rem auto;
}
  article.single {
    border-top: .2vh dotted #2d7474;
    margin: -6rem auto 1rem auto;
    background: #f0f0ea;
    padding: 2rem;
  }
  article p:last-child {
    margin-bottom: 1rem;
  }
p {
  padding: 0 .5rem;
  margin-left: 3rem;
}
  p + p,
  figure + p {
    margin-top: 2rem;
  }

blockquote {
  background-color: #e3e1e1;
  border-left: .5vw solid #2d7474;
  display: flex;
  flex-direction: column;
  align-items: center;
  padding: 1rem;
  margin: 1.5rem;
}
  blockquote cite {
    font-style: italic;
  }
  blockquote p {
    margin-left: 0;
  }

figure {
  border-top: .2vh solid #2d7474;
  background-color: #e3e1e1;
  text-align: center;
  padding: 1.5rem 0;
  margin: 1rem 0 0;
  font-size: 1.5rem;
  width: 100%;
}
  figure img {
    max-width: 250px;
    max-height: 250px;
    border: .5vw solid #323a45;
    padding: 1px;
  }
figcaption {
  padding: 1rem;
  line-height: 1.4;
}
aside {
  display: flex;
  flex-direction: column;
  background-color: #e3e1e1;
  padding: 1rem 0;
  border-bottom: .2vh solid #07486c;
}
  aside p {
    max-width: 50rem;
    margin: 0 auto;
  }

/* https://fvsch.com/code/css-locks/ */
p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  font-size: 1rem;
  line-height: calc( 1.5em + 0.2 * 1rem );
}
h1 {
  font-size: 1.9rem;
  line-height: calc( 1.2em + 0.2 * 1rem );
}
h2 {
  font-size: 1.6rem;
  line-height: calc( 1.3em + 0.2 * 1rem );
}
h3 {
  font-size: 1.35rem;
  line-height: calc( 1.4em + 0.2 * 1rem );
}
@media (min-width: 20em) {
  /* The (100vw - 20rem) / (50 - 20) part
     resolves to 0-1rem, depending on the
     viewport width (between 20em and 50em). */
  p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
    font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
    margin-left: 0;
  }
  h1 {
    font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
  h2 {
    font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
  h3 {
    font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
}
@media (min-width: 50em) {
  /* The right part of the addition *must* be a
     rem value. In this example we *could* change
     the whole declaration to font-size:2.5rem,
     but if our baseline value was not expressed
     in rem we would have to use calc. */
  p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
    font-size: calc( 1rem + .6 * 1rem );
    line-height: 1.5em;
  }
  p, li, pre, details {
    margin-left: 3rem;
  }
  h1 {
    font-size: calc( 1.9rem + 1.5 * 1rem );
    line-height: 1.2em;
  }
  h2 {
    font-size: calc( 1.5rem + 1.5 * 1rem );
    line-height: 1.3em;
  }
  h3 {
    font-size: calc( 1.35rem + 1.5 * 1rem );
    line-height: 1.4em;
  }
  figure img {
    max-width: 500px;
    max-height: 500px;
  }
}

figure.unsquared {
  margin-bottom: 1.5rem;
}
  figure.unsquared img {
    height: inherit;
  }


@media print {
  body { font-size: 100%; }
  a:after { content: " (" attr(href) ")"; }
  a, a:link, a:visited, a:after {
    text-decoration: underline;
    text-shadow: none !important;
    background-image: none !important;
    background: white;
    color: black;
  }
  abbr[title] { border-bottom: 0; }
  abbr[title]:after { content: " (" attr(title) ")"; }
  img { page-break-inside: avoid; }
  @page { margin: 2cm .5cm; }
  h1, h2, h3 { page-break-after: avoid; }
  p3 { orphans: 3; widows: 3; }
  img {
    max-width: 250px !important;
    max-height: 250px !important;
  }
  nav, aside { display: none; }
}

ul.with_columns {
  column-count: 1;
}
@media (min-width: 20em) {
  ul.with_columns {
    column-count: 2;
  }
}
@media (min-width: 50em) {
  ul.with_columns {
    column-count: 3;
  }
}
ul.with_two_columns {
  column-count: 1;
}
@media (min-width: 20em) {
  ul.with_two_columns {
    column-count: 1;
  }
}
@media (min-width: 50em) {
  ul.with_two_columns {
    column-count: 2;
  }
}

.gallery {
  display: flex;
  flex-wrap: wrap;
  justify-content: space-around;
}
  .gallery figure img {
    margin-left: 1rem;
    margin-right: 1rem;
  }
  .gallery figure figcaption {
    font-family: 'ConcourseT3'
  }

footer {
  font-family: 'ConcourseT3';
  display: flex;
  flex-direction: column;
  border-top: 3px solid white;
  padding: 4rem 0;
  background-color: #07486c;
  color: white;
}
  footer > * {
    max-width: 50rem;
    margin: 0 auto;
  }
  footer a {
    color: #f1c40f;
  }
  footer .avatar {
    width: 200px;
    height: 200px;
    border-radius: 50%;
    float: left;
    -webkit-shape-outside: circle();
    shape-outside: circle();
    margin-right: 2rem;
    padding: 2px 5px 5px 2px;
    background: white;
    border-left: 1px solid #f1c40f;
    border-top: 1px solid #f1c40f;
    border-right: 5px solid #f1c40f;
    border-bottom: 5px solid #f1c40f;
  }
</style>

<h1>
  <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  The billionaire’s typewriter (archive)
  <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
</h1>
<section>
  <article>
    <h3><a href="http://practicaltypography.com/billionaires-typewriter.html">Source originale du contenu</a></h3>
    <div id="doc"><p>A friend pointed me to a story on Medium called <a href="https://medium.com/designing-medium/death-to-typewriters-9b7712847639">“Death to Typewriters,”</a> by Medium designer <a href="https://medium.com/@mwichary">Marcin Wichary.</a> The story is about the influence of the typewriter on digital typesetting. It references my “excellent list” of <a href="typewriter-habits.html" class="xref">typewriter habits</a>.</p><p>Thank you for the compliment, Mr. Wichary. I can’t quibble with the details of your piece. It’s true that Medium and I are opposed to certain typographic shortcuts imported from the <span class="no-hyphens">typewriter.</span></p><p>But by the end, I realized I disagree deeply with Medium about the ethics of design. And by ethics, I mean something simple: though Medium and I are both making tools for writers, what I want for writers and what Medium wants couldn’t be more different. Medium may be avoiding what made the typewriter bad, but it’s also avoiding what made it good. Writers who are tempted to use Medium—or similar publishing tools—should be conscious of these <span class="no-hyphens">tradeoffs.</span></p><p>So, a few words about <span class="no-hyphens">that.</span></p><div style="height:1em"></div><p>For those who don’t incessantly follow Internet startups, <a href="http://medium.com">Medium</a> is a blogging service run by one of the founders of Twitter, multibillionaire <a href="https://medium.com/@ev">Evan Williams.</a> Though it owes much to blogging services of the past (including <a href="http://en.wikipedia.org/wiki/Blogger_%28service%29">Blogger,</a> also founded by Mr. Williams), Medium is oriented toward longer, less diaristic <span class="no-hyphens">stories.</span></p><p>Medium also differs from earlier blogging services in a significant, contrarian way: it offers you, the writer, nearly zero options for the presentation of your stories. No matter what kind of story you write, or who your readers are, it gets packaged into a single, non-negotiable <span class="no-hyphens">template.</span></p><p>Medium isn’t the only blogging service riding this wave, though so far it seems to have the biggest surfboard. Others include <a href="http://svbtle.com">Svbtle,</a> <a href="http://postagon.com">Postagon,</a> and <a href="http://silvrback.com">Silvrback.</a> They all promote a similarly constrained approach to design, which is sometimes called <a href="https://www.postagon.com">minimalist.</a></p><div class="subhead">Minimalist vs. homogeneous design</div><p>As a fan of minimalism, however, I think that term is misapplied here. Minimalism doesn’t foreclose either expressive breadth or conceptual depth. On the contrary, the minimalist program—as it initially emerged in fine art of the 20th century—has been about diverting the viewer’s attention from overt signs of authorship to the deeper purity of the <span class="no-hyphens">ingredients.</span></p><aside>Ad Reinhardt with some of his amazing <a href="http://www.guggenheim.org/new-york/collections/collection-online/artwork/3698">black paintings.</a> (Spoiler alert: they’re not entirely <span class="no-hyphens">monochromatic.)</span></aside><p><img src="http://practicaltypography.com/images/reinhardt.jpeg" /></p><aside>Bryan Garner notes that <em>homogeneous</em> is frequently misspelled <em>homogenous</em>, and has five syllables that are frequently mispronounced as four. (<a href="http://www.amazon.com/Garners-Modern-American-Usage-Garner/dp/0195382757">GMAU 3rd ed.</a> at <span class="no-hyphens">425.)</span></aside><p>If that’s the case, we can’t say that Medium et al. are offering minimalist design. Only the veneer is minimalist. What they’re really offering is a shift from design as a choice to design as a constant. Instead of minimalist design, a better term might be <em>homogeneous</em> <span class="no-hyphens">design.</span></p><p>On the one hand, Medium’s homogeneous design works and reads well. Members of Medium’s design team have <a href="https://medium.com/designing-medium">catalogued the many typographic details</a> they’ve implemented. Good for them. If they <a href="https://medium.com/@verbagetruck/dustin-senos-typesets-the-future-86fd91e9b6ee">sometimes act</a> as if they discovered typography like it was the Higgs boson, we can forgive their excess of enthusiasm. Bringing these details to a wider audience, and raising standards for typography on the web generally, is a worthy <span class="no-hyphens">project.</span></p><p>On the other hand, a necessary side effect of Medium’s homogeneous design is that every story looks the same. If you agree that the role of typography is to enhance the text for the benefit of the reader (as I contend in <a href="who-is-typography-for.html" class="xref">who is typography for?</a>), then it stands to reason that different texts demand distinct typography. As I say in <a href="what-is-good-typography.html" class="xref">What is Good Typography?</a>, one size never fits all. Typography wants to be <span class="no-hyphens">heterogeneous.</span></p><div class="subhead">Delicious but not nutritious</div><p>Still, I wouldn’t say that Medium’s homogeneous design is bad <em>ex ante</em>. Among web-publishing tools, I see Medium as the equivalent of a frozen pizza: not as wholesome as a meal you could make yourself, but for those without the time or motivation to cook, a potentially better option than just eating peanut butter straight from the <span class="no-hyphens">jar.</span></p><aside><dquo>“You don’t need to see our formatting </dquo><span class="no-hyphens">options.”</span></aside><p><img src="http://practicaltypography.com/images/obi-wan.jpg" /></p><p>The problem, however, is that Medium holds out its homogeneous design as more than a frozen pizza. It has become, by the Jedi mind trickery favored by today’s tech companies, a Bellagio buffet of delicious <span class="no-hyphens">nonsense:</span></p><ol><li><p>Evan Williams <a href="https://medium.com/about/what-were-trying-to-do-with-medium-e2f5bfcf0434">frames Medium</a> as a “place for ideas” with an “ethos” of “openness and democracy—like the Internet itself.” Fine, but idealistic platitudes explain nothing. How, specifically, does Medium improve the <span class="no-hyphens">Internet?</span></p></li><li><p>Mr. Williams <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">claims</a> that Medium is “the best writing tool on the web.” Okay, that’s at least concrete. But we’ve got a lot of good web-based writing tools already. Medium does more than <span class="no-hyphens">those?</span></p></li><li><p>Actually, no—Mr. Williams <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">concedes</a> that Medium has “stripped out a lot of the power that other editors give you.” So how is it possible to be “the best” while offering <span class="no-hyphens">less?</span></p></li><li><p>Here, Mr. Williams <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">parries</a>—he claims that thinking about the presentation of your work is “a terrible distraction and a waste of time.” <span class="no-hyphens">Why?</span></p></li><li><p>Apparently <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">because he’s</a> “one of those people who will open up Word and spend half [his] time defining styles and adjusting the spacing between paragraphs.” Hmm, not everyone has that problem with <span class="no-hyphens">Word.</span></p></li><li><p>Now comes the hand-waving, as Mr. Williams assures us that Medium’s homogeneous design isn’t a limitation—it’s <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">in fact essential</a> to let your “brilliance and creativity flow smoothly onto the <span class="no-hyphens">screen.”</span></p></li><li><p>Moreover, anyone who disagrees <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">is a Luddite</a>—because “everything [other than Medium] feels like stepping back in <span class="no-hyphens">time.”</span></p></li></ol><p>Like all nonsense, it’s intended to be easy to swallow. But Mr. Williams’s argument is flawed in at least three <span class="no-hyphens">ways:</span></p><ol><li><p><strong>It makes no sense in the context of today’s web</strong>. If Medium had launched 10 years ago, it would’ve been astonishing. But it didn’t. Today, the costs of web publishing—including design—have declined to almost zero. Relative to today’s web, Medium is not creating new possibilities, but instead closing them off. To prevail, Medium needs to persuade you that you don’t care about the broader expressive possibilities of web <span class="no-hyphens">publishing.</span></p></li><li><p><strong>It sets up a false dichotomy about writing tools</strong>. Mr. Williams depicts the writer’s choice as Medium vs. complicated tools like Word. Not accurate. First, different tools exist for different needs. It would be silly to use Word to make a web page, but equally silly to use Medium to prepare a print-on-demand paperback. Second, anyone who’s used current blogging tools appreciates that web publishing has become heavily automated. Much of the formatting can be handled automatically (e.g., via <a href="https://wordpress.org/themes/">WordPress themes</a>) or manually, as you <span class="no-hyphens">prefer.</span></p></li><li><p><strong>You’re giving up far more than design choice</strong>. Mr. Williams <a href="https://medium.com/about/writing-in-medium-df8eac9f4a5e">describes</a> Medium’s key benefit as rescuing writers from the “terrible distraction” of formatting chores. But consider the cost. Though he’s baiting the hook with design, he’s also asking you, the writer, to let him control how you offer your work to readers. Meaning, to get the full benefit of Medium’s design, you have to let your story live on Medium, send all your readers to Medium, have your work permanently entangled with other stories on Medium, and so on—a significant <span class="no-hyphens">concession.</span></p></li></ol><p>As for that entanglement among stories, Mr. Williams <a href="https://medium.com/@ev/sarah-lacys-latest-medium-me-critique-makes-no-sense-1917c67405ca">has conceded</a> that it’s “confusing.” But this ambiguity isn’t a bug. It’s an essential feature of the business plan. The goal is to create the illusion that everything on Medium belongs to one editorial ecosystem, as if it were the New York <em>Times</em>.</p><aside>No word yet on how Medium’s <a href="https://medium.com/policy/medium-privacy-policy-f03bf92035c9">surveillance policies</a> square with all that openness and <span class="no-hyphens">democracy.</span></aside><p>But unlike the <em>Times</em>, Medium pays for <a href="https://medium.com/@ev/what-is-now-the-matter-at-medium-105a334f2ea">only a small fraction</a> of its stories. The rest are submitted—for free—by writers like you. After a long time <a href="http://www.theatlantic.com/technology/archive/2013/08/what-is-medium/278965/">being elusive</a> about its business model, Medium revealed that it plans to make money by—surprise!—<a href="http://adage.com/article/digital/bmw-runs-ads-medium-twitter-founders-platform/294321/">selling advertising.</a> This means displaying ads, but also collecting and selling data about readers and writers. So Medium will extract revenue from every story, whether it paid for that story or not. (By the way, will that revenue be shared with writers? <a href="https://medium.com/inside/there-will-be-money-d80f7d0178a9">Um, no.</a>)</p><p>And coming full circle—what’s the indispensable tool for creating this illusion of an editorial ecosystem? The homogeneous design. The butterfly ballot of 2000 (depicted in <a href="why-typography-matters.html" class="xref">Why typography matters</a>) proved that errors of typography can have historic consequences. Medium proves that typography can be used as a tool of economic leverage and <span class="no-hyphens">control.</span></p><p>In truth, Medium’s main product is not a publishing platform, but the promotion of a publishing platform. This promotion brings readers and writers onto the site. This, in turn, generates the usage data that’s valuable to advertisers. Boiled down, Medium is simply marketing in the service of more marketing. It is not a “place for ideas.” It is a place for advertisers. It is, therefore, utterly <span class="no-hyphens">superfluous.</span></p><p><dquo>“But what about all the writing on Medium?” The measure of superfluity is not the writing on Medium. Rather, it’s what Medium </dquo><em>adds</em> to the writing. Recall the question from above: how does Medium improve the Internet? I haven’t seen a single story on Medium that couldn’t exist equally well elsewhere. Nor evidence that Medium’s editing and publishing tools are a manifest improvement over what you can do with other <span class="no-hyphens">tools.</span></p><p>In sum—still <span class="no-hyphens">superfluous.</span></p><div class="subhead">What we can learn from typewriters</div><aside><img src="http://practicaltypography.com/images/olivetti.jpeg" /> Olivetti was famous for its <a href="https://www.flickr.com/photos/19855494@N00/sets/72157603713300507/">graphic and advertising design</a> as well as its <span class="no-hyphens">typewriters.</span></aside><p>Let’s remember two points that get lost among the torches and pitchforks carried by <a href="https://medium.com/designing-medium/death-to-typewriters-9b7712847639">“Death to <span class="no-hyphens">Typewriters.”</span></a></p><p>First, although the typewriter did impose homogeneous (and ugly) typography, it had excellent ethics. The typewriter made it possible to write more quickly, legibly, and accurately than ever before, with low cost and high portability. In short, it offered freedom. For that, homogeneous design was a small price to <span class="no-hyphens">pay.</span></p><p>Second, though typewriter typography was terrible, it wasn’t a choice made by typewriter manufacturers out of laziness or ignorance. These compromises were necessitated by the mechanical limitations of the typewriter. Typewriters were never ideal, but as certain limitations were overcome, they got <span class="no-hyphens">better.</span></p><aside>IBM invented the “type ball” technology that made it possible to use different fonts in a typewriter. I studied this one as part of my research for <a href="triplicate.html" class="xref">Triplicate</a>.</aside><p><img src="http://practicaltypography.com/images/selectric-ball.jpeg" /></p><p>With today’s networked computers, we’re getting closer to the ideal. We enjoy the benefits of the typewriter without any of its limitations. We get more efficiency, speed, storage, design options, and freedom. The computer is the most remarkable device in the 500-year history of printing (which already includes a lot of remarkable <span class="no-hyphens">devices).</span></p><p>This leads back to why those <a href="typewriter-habits.html" class="xref">typewriter habits</a> are so awful in the digital age. Computers have none of the mechanical limitations of typewriters. So the typographic shortcuts that were a necessary evil with typewriters are likewise obsolete. Why perpetuate <span class="no-hyphens">them?</span></p><aside>For more on this, see <a href="http://typo.la/rtde">“Reversing the Tide of Declining <span class="no-hyphens">Expectations.”</span></a></aside><p>I rely on a broader version of this principle in my own work. Technology keeps improving, thereby expanding possibilities for us. So we have a choice. We can either ignore those possibilities, and merely accept what technology offers, which will ultimately make us lazy. Or we can explore those new possibilities. But to do that, we need to expect more of <span class="no-hyphens">ourselves.</span></p><p>We also need better tools. I’d characterize most of my work as toolsmithing—whether the project is <a href="http://concoursefont.com">designing a font,</a> <a href="http://practicaltypography.com">writing a book,</a> or <a href="http://pollenpub.com">creating publishing software.</a> I don’t control how others use these tools. I don’t want to, either. For me, it’s far more interesting to share these tools and then be surprised by how others use <span class="no-hyphens">them.</span></p><p>To that end, I deliberately avoid creating tools that do too much. Some assembly is always required. For instance, I’ll tell you the qualities of good <a href="websites.html" class="xref">website</a> typography, but I’m not going to sell you a template. I want the customers for my tools to be responsible for some of the heavy lifting. That way, they discover that what they get out of the tool has a connection to what they put <span class="no-hyphens">in.</span></p><p>So even though I oppose the <a href="typewriter-habits.html" class="xref">typewriter habits</a>, I still appreciate that core ethic of the typewriter—removing limitations when you can, doing your best with them when you can’t. That’s a great idea. Yes, let’s explore all the possibilities of the technology available to us. Let’s hack the hell out of everything and see what happens. In the typewriter era, the technological limitations were mostly hardware. Today, mostly software. But if we treat these limitations as something to obey—not overcome—we’ll just become indentured to whoever controls that <span class="no-hyphens">technology.</span></p><div class="subhead">What we can learn from Medium</div><p>In <a href="https://medium.com/designing-medium/death-to-typewriters-9b7712847639">“Death to Typewriters,”</a> Medium insists that the typewriter is its “sworn enemy.” In certain typographic details, maybe so. But as a device that imposes homogeneous design, Medium still has a lot in common with the <span class="no-hyphens">typewriter.</span></p><p>In fact, its ethics are actually <em>worse</em> than the traditional typewriter. Why? Because Medium’s homogeneous design has nothing to do with limitations of the underlying technology (in this case, the web). As discussed above, it’s a deliberate choice that lets Medium extract value from the talent and labor of <span class="no-hyphens">others.</span></p><p>Medium is a new kind of typewriter—the billionaire’s typewriter. It’s not the only billionaire’s typewriter. So is the Kindle. So is iBooks. So is Twitter. What distinguishes these new typewriters is not the possibilities they make available to writers, but what they take <span class="no-hyphens">away.</span></p><p><strong>Whereas the traditional typewriter offered freedom at the cost of design, the billionaire’s typewriter offers convenience at the cost of <span class="no-hyphens">freedom.</span></strong></p><p>As a writer and toolsmith, I’ve found the rush to embrace these systems perplexing. Not because I’m curmudgeonly. Not because I fail to understand that people, including writers, enjoy things that are free and <span class="no-hyphens">convenient.</span></p><p>Rather, because gentle scrutiny reveals that these systems are powered by a form of human fracking. To get his fracking permit on your territory, Mr. Williams (the multibillionaire) needs to persuade you (the writer) that a key consideration in your work (namely, how &amp; where you offer it to readers) is a “waste of <span class="no-hyphens">time.”</span></p><p>If you really believe that, then by all means, keep using the billionaire’s <span class="no-hyphens">typewriter.</span></p><div style="height:1em"></div><p>But if you have doubts, here’s a <span class="no-hyphens">counterproposal.</span></p><p>As a writer, the biggest potential waste of your time is not typography chores, but Medium itself. Because in return for that snazzy design, Medium needs you to relinquish control of how your work gets to <span class="no-hyphens">readers.</span></p><p>Tempting perhaps. But where does it lead? I fear that writers who limit themselves to providing “content” for someone else’s “branded platform” are going to end up with as much leverage as cows on a dairy farm. (A problem at the core of the recent <a href="http://www.vanityfair.com/news/business/2014/12/amazon-hachette-ebook-publishing">Hachette–Amazon dispute.</a>)</p><p>If you want to be part of something open and democratic, use open-source software. If you want to have your writing look great, learn something about typography (or hire a designer). If you need a platform for writing, try <a href="http://pollenpub.com">Pollen</a> (the system I made for this site), or <a href="http://wordpress.org">WordPress,</a> or a subscription service like <a href="http://svbtle.com">Svbtle.</a> I prefer web publishing despite <a href="economics-year-one.html">its shortcomings,</a> but if you don’t, then make an e-book or PDF and distribute it <span class="no-hyphens">yourself.</span></p><p>As writers, we don’t need companies like Medium to tell us how to use the web. Or define openness and democracy. Or tell us what’s a “waste of [our] time” and what’s not. Or determine how and where readers experience our work. We need to decide those things for <span class="no-hyphens">ourselves.</span></p><p><sig>—Matthew Butterick<br />17 Feb <span class="no-hyphens">2015</span></sig></p><div class="btw"><div class="btw-title">by the way</div><ul><li><p>Though I’ve been poking holes in its rhetoric, I don’t have antipathy toward Medium any more than I do <a href="http://typographyforlawyers.com/why-google-web-fonts-arent-really-open-source.html">Google Fonts.</a> I get it—it’s a company set up to make money. It’s not a literary foundation. I’m sure the people involved with it are talented and sincere. And they certainly don’t care what I <span class="no-hyphens">think.</span></p></li><li><p>A couple readers have pointed out that Medium doesn’t require exclusivity—you own your stories, and you can publish them elsewhere. Fair enough. But this doesn’t change the core argument. Medium is definitely <a href="https://medium.com/@Medium/medium-connects-the-people-stories-and-ideas-that-matter-to-you-495655fb8459">pitching itself to writers</a> as an all-inclusive platform (“Build your publication, blog, or writing portfolio”). As for those writers who are using it as a secondary outlet, Medium is still extracting revenue from their stories that isn’t <span class="no-hyphens">shared.</span></p></li><li><p>I’m not the first to raise these issues. See also <a href="http://www.elezea.com/2013/08/medium-is-eating-all-the-content/">Rian van der Merwe</a> (“Medium seems to be more about Medium than about authors … The barrier to setting up your own site has never been lower”), <a href="http://www.marco.org/2013/08/05/be-your-own-platform">Marco Arment</a> (“consider whether it’s wise to invest your time and writing in someone else’s platform for free”), and <a href="http://www.theatlantic.com/technology/archive/2013/08/what-is-medium/278965/">Alexis Madrigal</a> (“media producers … have to decide whether Medium is a friend or a <span class="no-hyphens">foe”).</span></p></li><li><p>Confidential to graphic designers <a href="https://medium.com/vvvvvv-studio/albers-in-command-b3184edd7746">who are publishing stories</a> on Medium: if you wouldn’t set your <a href="business-cards.html" class="xref">business cards</a> in <a href="times-new-roman.html" class="xref">Times New Roman</a>, then why would you … ah, forget <span class="no-hyphens">it.</span></p></li></ul></div></div>

<p><a id="links"></a><div style="height:1em"></div><ul class="children"></ul></p>
  </article>
</section>


<nav id="jumpto">
  <p>
    <a href="/david/blog/">Accueil du blog</a> |
    <a href="http://practicaltypography.com/billionaires-typewriter.html">Source originale</a> |
    <a href="/david/stream/2019/">Accueil du flux</a>
  </p>
</nav>

<footer>
  <div>
    <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
    <p>
      Bonjour/Hi!
      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>
      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>).
    </p>
    <p>
      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>.
    </p>
    
    <p>
      Voici quelques articles choisis :
      <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
      <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
      <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
      <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
      <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
      <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
      <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
      <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
      <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
      <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
      <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
      <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
      <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
      <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
      <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
      et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
    </p>
    <p>
      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>.
    </p>
    <p>
      Je ne traque pas ta navigation mais mon
      <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
      conserve des logs d’accès.
    </p>
  </div>
</footer>
<script type="text/javascript">
  ;(_ => {
    const jumper = document.getElementById('jumper')
    jumper.addEventListener('click', e => {
      e.preventDefault()
      const anchor = e.target.getAttribute('href')
      const targetEl = document.getElementById(anchor.substring(1))
      targetEl.scrollIntoView({behavior: 'smooth'})
    })
  })()
</script>