1 yıl önce · 391cbb0144
--- a/david/2023/01/13/index.html
+++ b/david/2023/01/13/index.html
@@ -81,7 +81,7 @@
        Recherche</a
      >
    </nobr>
    
     • <a rel="next" href="/david/2023/01/14/" title="Publication suivante : Dépendances">Suivant →</a>
  </p>
 </nav>
 <hr>
@@ -125,7 +125,7 @@
  <p class="center">
    <a rel="prev" href="/david/2023/01/12/" title="Publication précédente : Masque">← Précédent</a> •
    <a href="/david/2023/" title="Liste des publications récentes">↑ En 2023</a>
    
     • <a rel="next" href="/david/2023/01/14/" title="Publication suivante : Dépendances">Suivant →</a>
  </p>
 </nav>
 </article>
--- a/david/2023/01/14/index.html
+++ b/david/2023/01/14/index.html
@@ -0,0 +1,287 @@
 <!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` element
  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,initial-scale=1">
 <!-- Required to make a valid HTML5 document. -->
 <title>Dépendances — David Larlet</title>
 <meta name="description" content="I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so it’s not very attractive for new maintainers.">
 <!-- That good ol' feed, subscribe :). -->
 <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
 <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
 <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
 <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
 <link rel="manifest" href="/static/david/icons2/site.webmanifest">
 <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
 <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
 <meta name="msapplication-TileColor" content="#f7f7f7">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
 <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
 <!-- Documented, feel free to shoot an email. -->
 <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
 <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
 <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>
 <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>
 <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>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
 <script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
 </script>

 <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


 <article>
 <header>
  <h1>Dépendances</h1>
 </header>
 <nav>
  <p class="center">
    <a rel="prev" href="/david/2023/01/13/" title="Publication précédente : Eaux&nbsp;grises">← Précédent</a> •
    <nobr>
      <a href="/david/" title="Aller à l’accueil"
        ><svg class="icon icon-home">
          <use
            xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-home"
          ></use>
        </svg>
        Accueil</a
      >
    </nobr>
    •
    <nobr>
      <a href="/david/recherche/" title="Aller à la page de recherche"
        ><svg class="icon icon-search">
          <use
            xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-search"
          ></use>
        </svg>
        Recherche</a
      >
    </nobr>
    
  </p>
 </nav>
 <hr>


 <blockquote lang="en">
 <p>I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so <mark>it’s not very attractive for new&nbsp;maintainers.</mark></p>
 <p><cite><em><a href="https://nolanlawson.com/2023/01/09/retiring-pinafore/">Retiring Pinafore</a></em>&nbsp;(<a href="/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/">cache</a>)</cite></p>
 </blockquote>
 <p>«&nbsp;<span lang=en>Move fast and outdate things.</span>&nbsp;» n’est pas un <em>motto</em> mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son <a href="https://www.baldurbjarnason.com/">site</a>, son <a href="https://softwarecrisis.baldurbjarnason.com/">livre</a> ou sa <a href="https://softwarecrisis.dev/">newsletter</a>.</p>
 <p>Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique&nbsp;notamment.</p>
 <p>2023, l’année de la maturité&nbsp;😂.</p>

 <blockquote lang="en">
 <p>The symptoms of pop&nbsp;culture:</p>
 <ul>
 <li>A “disdain for history”. Pop cultures believe history doesn’t have anything to teach&nbsp;them.</li>
 <li>Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently&nbsp;inferior.</li>
 <li><mark>What’s next is going to be superior to what’s now.</mark> Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in&nbsp;progress.</li>
 <li>The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be&nbsp;right.</li>
 </ul>
 <p>These traits are deeply irrational but they are the tech industry’s default mode of&nbsp;operation.</p>
 <p><cite><em><a href="https://softwarecrisis.dev/letters/tech-is-a-pop-culture/">Tech Companies Are Irrational Pop Cultures</a></em>&nbsp;(<a href="/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/">cache</a>)</cite></p>
 </blockquote>
 <hr />

 <blockquote lang="en">
 <p>We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. <mark>A dependency you use breaks when one of its dependencies stops working,</mark> leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned&nbsp;around.</p>
 <p>All of which is bad enough but also misses the&nbsp;point.</p>
 <p><cite><em><a href="https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/">The Open-Source Software bubble that is and the blogging bubble that was</a></em>&nbsp;(<a href="/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/">cache</a>)</cite></p>
 </blockquote>

 <blockquote>
 <p>This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), <mark>that’s a pretty small slice of a much larger&nbsp;community.</mark></p>
 <p>We seem to live in different&nbsp;worlds.</p>
 <p><cite><em><a href="https://www.zachleat.com/web/javascript-community/">JavaScript, Community</a></em>&nbsp;(<a href="/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/">cache</a>)</cite></p>
 </blockquote>


  <nav>
    <p>
      
        <a href="/david/2023/gratitude/"
          title="Liste de tous les articles 2023 associés à cette étiquette"
          >#gratitude</a>
      
        <a href="/david/2023/recherche/"
          title="Liste de tous les articles 2023 associés à cette étiquette"
          >#recherche</a>
      
        <a href="/david/2023/technique/"
          title="Liste de tous les articles 2023 associés à cette étiquette"
          >#technique</a>
      
      <a href="/david/#tags-2023"
        title="Liste de toutes les étiquettes 2023"
        ><svg class="icon icon-tags">
          <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-tags"></use>
        </svg>
        tous ?</a
      >
    </p>
  </nav>

 <nav>
  <p class="center">
    <a rel="prev" href="/david/2023/01/13/" title="Publication précédente : Eaux&nbsp;grises">← Précédent</a> •
    <a href="/david/2023/" title="Liste des publications récentes">↑ En 2023</a>
    
  </p>
 </nav>
 </article>


 <hr>

 <footer>
  <p>
    <nobr>
      <a href="/david/" title="Aller à l’accueil"
        ><svg class="icon icon-home">
          <use
            xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-home"
          ></use>
        </svg>
        Accueil</a
      >
    </nobr>
    •
    <nobr>
      <a href="/david/log/" title="Accès au flux RSS"
        ><svg class="icon icon-rss2">
          <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-rss2"></use>
        </svg>
        Suivre</a
      >
    </nobr>
    •
    <nobr>
      <a href="http://larlet.com" title="Go to my English profile" data-instant
        ><svg class="icon icon-user-tie">
          <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-user-tie"></use>
        </svg>
        Pro</a
      >
    </nobr>
    •
    <nobr>
      <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"
        ><svg class="icon icon-mail">
          <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-mail"></use>
        </svg>
        Email</a
      >
    </nobr>
    •
    <nobr>
      <abbr
        class="nowrap"
        title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"
        ><svg class="icon icon-hammer2">
          <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-hammer2"></use>
        </svg>
        Légal</abbr
      >
    </nobr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs-2022-03.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
 </footer>
 <script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
 <script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
 </script>

 </body>
 </html>
--- a/david/2023/_sources/2023-01-14
+++ b/david/2023/_sources/2023-01-14
@@ -0,0 +1,40 @@
 # Dépendances

 > [en] I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so ==it’s not very attractive for new maintainers.==
 >
 > <cite>*[Retiring Pinafore](https://nolanlawson.com/2023/01/09/retiring-pinafore/)* ([cache](/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/))</cite>

 « <span lang=en>Move fast and outdate things.</span> » n’est pas un *motto* mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son [site](https://www.baldurbjarnason.com/), son [livre](https://softwarecrisis.baldurbjarnason.com/) ou sa [newsletter](https://softwarecrisis.dev/).

 Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique notamment.

 2023, l’année de la maturité 😂.

 > [en] The symptoms of pop culture:
 > 
 > * A “disdain for history”. Pop cultures believe history doesn’t have anything to teach them.
 > * Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently inferior.
 > * ==What’s next is going to be superior to what’s now.== Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in progress.
 > * The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be right.
 >
 > These traits are deeply irrational but they are the tech industry’s default mode of operation.
 >
 > <cite>*[Tech Companies Are Irrational Pop Cultures](https://softwarecrisis.dev/letters/tech-is-a-pop-culture/)* ([cache](/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/))</cite>


 ---

 > [en] We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. ==A dependency you use breaks when one of its dependencies stops working,== leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned around.
 >
 > All of which is bad enough but also misses the point.
 >
 > <cite>*[The Open-Source Software bubble that is and the blogging bubble that was](https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/)* ([cache](/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/))</cite>

 > This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), ==that’s a pretty small slice of a much larger community.==
 >
 > We seem to live in different worlds.
 > 
 > <cite>*[JavaScript, Community](https://www.zachleat.com/web/javascript-community/)* ([cache](/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/))</cite>


 #gratitude #recherche #technique
--- a/david/2023/gratitude/index.html
+++ b/david/2023/gratitude/index.html
@@ -76,6 +76,46 @@
 <main>
  <p>Les plus récentes en premier, les 3 premières sont dépliées et ensuite c’est à la demande, bonne exploration !</p>
  
    <h2><a href="/david/2023/01/14/" title="Lien permanent vers cet article">Dépendances</a> (2023-01-14)</h2>
    
      

 <blockquote lang="en">
 <p>I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so <mark>it’s not very attractive for new&nbsp;maintainers.</mark></p>
 <p><cite><em><a href="https://nolanlawson.com/2023/01/09/retiring-pinafore/">Retiring Pinafore</a></em>&nbsp;(<a href="/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/">cache</a>)</cite></p>
 </blockquote>
 <p>«&nbsp;<span lang=en>Move fast and outdate things.</span>&nbsp;» n’est pas un <em>motto</em> mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son <a href="https://www.baldurbjarnason.com/">site</a>, son <a href="https://softwarecrisis.baldurbjarnason.com/">livre</a> ou sa <a href="https://softwarecrisis.dev/">newsletter</a>.</p>
 <p>Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique&nbsp;notamment.</p>
 <p>2023, l’année de la maturité&nbsp;😂.</p>

 <blockquote lang="en">
 <p>The symptoms of pop&nbsp;culture:</p>
 <ul>
 <li>A “disdain for history”. Pop cultures believe history doesn’t have anything to teach&nbsp;them.</li>
 <li>Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently&nbsp;inferior.</li>
 <li><mark>What’s next is going to be superior to what’s now.</mark> Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in&nbsp;progress.</li>
 <li>The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be&nbsp;right.</li>
 </ul>
 <p>These traits are deeply irrational but they are the tech industry’s default mode of&nbsp;operation.</p>
 <p><cite><em><a href="https://softwarecrisis.dev/letters/tech-is-a-pop-culture/">Tech Companies Are Irrational Pop Cultures</a></em>&nbsp;(<a href="/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/">cache</a>)</cite></p>
 </blockquote>
 <hr />

 <blockquote lang="en">
 <p>We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. <mark>A dependency you use breaks when one of its dependencies stops working,</mark> leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned&nbsp;around.</p>
 <p>All of which is bad enough but also misses the&nbsp;point.</p>
 <p><cite><em><a href="https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/">The Open-Source Software bubble that is and the blogging bubble that was</a></em>&nbsp;(<a href="/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/">cache</a>)</cite></p>
 </blockquote>

 <blockquote>
 <p>This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), <mark>that’s a pretty small slice of a much larger&nbsp;community.</mark></p>
 <p>We seem to live in different&nbsp;worlds.</p>
 <p><cite><em><a href="https://www.zachleat.com/web/javascript-community/">JavaScript, Community</a></em>&nbsp;(<a href="/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/">cache</a>)</cite></p>
 </blockquote>

    

  
    <h2><a href="/david/2023/01/06/" title="Lien permanent vers cet article">Toile</a> (2023-01-06)</h2>
    
      
--- a/david/2023/index.html
+++ b/david/2023/index.html
@@ -98,7 +98,8 @@
      <a href="/david/2023/01/10/">Qualité</a>, 
      <a href="/david/2023/01/11/">Suspendu</a>, 
      <a href="/david/2023/01/12/">Masque</a>, 
      <a href="/david/2023/01/13/">Eaux&nbsp;grises</a>.
      <a href="/david/2023/01/13/">Eaux&nbsp;grises</a>, 
      <a href="/david/2023/01/14/">Dépendances</a>.
      
    </p>
  
@@ -118,18 +119,18 @@
      <a href="/david/2021/don/">#don (1)</a>
      <a href="/david/2021/eau/">#eau (1)</a>
      <a href="/david/2021/gafam/">#gafam (1)</a>
      <a href="/david/2021/gratitude/">#gratitude (1)</a>
      <a href="/david/2021/gratitude/">#gratitude (2)</a>
      <a href="/david/2021/masque/">#masque (1)</a>
      <a href="/david/2021/mastodon/">#mastodon (1)</a>
      <a href="/david/2021/partage/">#partage (1)</a>
      <a href="/david/2021/photographie/">#photographie (1)</a>
      <a href="/david/2021/propriete/">#propriété (1)</a>
      <a href="/david/2021/qualite/">#qualité (1)</a>
      <a href="/david/2021/recherche/">#recherche (4)</a>
      <a href="/david/2021/recherche/">#recherche (5)</a>
      <a href="/david/2021/recyclage/">#recyclage (1)</a>
      <a href="/david/2021/reponse/">#réponse (2)</a>
      <a href="/david/2021/sport/">#sport (2)</a>
      <a href="/david/2021/technique/">#technique (3)</a>
      <a href="/david/2021/technique/">#technique (4)</a>
      <a href="/david/2021/traces/">#traces (1)</a>
      <a href="/david/2021/web/">#web (1)</a>
      
--- a/david/2023/recherche/index.html
+++ b/david/2023/recherche/index.html
@@ -76,6 +76,46 @@
 <main>
  <p>Les plus récentes en premier, les 3 premières sont dépliées et ensuite c’est à la demande, bonne exploration !</p>
  
    <h2><a href="/david/2023/01/14/" title="Lien permanent vers cet article">Dépendances</a> (2023-01-14)</h2>
    
      

 <blockquote lang="en">
 <p>I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so <mark>it’s not very attractive for new&nbsp;maintainers.</mark></p>
 <p><cite><em><a href="https://nolanlawson.com/2023/01/09/retiring-pinafore/">Retiring Pinafore</a></em>&nbsp;(<a href="/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/">cache</a>)</cite></p>
 </blockquote>
 <p>«&nbsp;<span lang=en>Move fast and outdate things.</span>&nbsp;» n’est pas un <em>motto</em> mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son <a href="https://www.baldurbjarnason.com/">site</a>, son <a href="https://softwarecrisis.baldurbjarnason.com/">livre</a> ou sa <a href="https://softwarecrisis.dev/">newsletter</a>.</p>
 <p>Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique&nbsp;notamment.</p>
 <p>2023, l’année de la maturité&nbsp;😂.</p>

 <blockquote lang="en">
 <p>The symptoms of pop&nbsp;culture:</p>
 <ul>
 <li>A “disdain for history”. Pop cultures believe history doesn’t have anything to teach&nbsp;them.</li>
 <li>Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently&nbsp;inferior.</li>
 <li><mark>What’s next is going to be superior to what’s now.</mark> Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in&nbsp;progress.</li>
 <li>The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be&nbsp;right.</li>
 </ul>
 <p>These traits are deeply irrational but they are the tech industry’s default mode of&nbsp;operation.</p>
 <p><cite><em><a href="https://softwarecrisis.dev/letters/tech-is-a-pop-culture/">Tech Companies Are Irrational Pop Cultures</a></em>&nbsp;(<a href="/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/">cache</a>)</cite></p>
 </blockquote>
 <hr />

 <blockquote lang="en">
 <p>We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. <mark>A dependency you use breaks when one of its dependencies stops working,</mark> leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned&nbsp;around.</p>
 <p>All of which is bad enough but also misses the&nbsp;point.</p>
 <p><cite><em><a href="https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/">The Open-Source Software bubble that is and the blogging bubble that was</a></em>&nbsp;(<a href="/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/">cache</a>)</cite></p>
 </blockquote>

 <blockquote>
 <p>This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), <mark>that’s a pretty small slice of a much larger&nbsp;community.</mark></p>
 <p>We seem to live in different&nbsp;worlds.</p>
 <p><cite><em><a href="https://www.zachleat.com/web/javascript-community/">JavaScript, Community</a></em>&nbsp;(<a href="/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/">cache</a>)</cite></p>
 </blockquote>

    

  
    <h2><a href="/david/2023/01/12/" title="Lien permanent vers cet article">Masque</a> (2023-01-12)</h2>
    
      
@@ -141,7 +181,9 @@
  
    <h2><a href="/david/2023/01/09/" title="Lien permanent vers cet article">Indépendant·e</a> (2023-01-09)</h2>
    
      
      <details>
        <summary>Déplier pour lire le contenu de la publication</summary>
        

 <blockquote>
 <p>2022&nbsp;était ma troisième année à mon compte. Alors, pour fêter ça, j’avais envie de faire un petit bilan de ce qui s’est passé cette année là pour moi, du côté&nbsp;professionnel.</p>
@@ -158,6 +200,7 @@
 <p><cite><em><a href="https://sebsauvage.net/links/?-wKcIw">J’ai un aveu à vous faire.</a></em>&nbsp;(<a href="/david/cache/2023/e976e16ee3e2dae4d644733ffb50fa9f/">cache</a>)</cite></p>
 </blockquote>

      </details>
    

  
--- a/david/2023/technique/index.html
+++ b/david/2023/technique/index.html
@@ -76,6 +76,46 @@
 <main>
  <p>Les plus récentes en premier, les 3 premières sont dépliées et ensuite c’est à la demande, bonne exploration !</p>
  
    <h2><a href="/david/2023/01/14/" title="Lien permanent vers cet article">Dépendances</a> (2023-01-14)</h2>
    
      

 <blockquote lang="en">
 <p>I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so <mark>it’s not very attractive for new&nbsp;maintainers.</mark></p>
 <p><cite><em><a href="https://nolanlawson.com/2023/01/09/retiring-pinafore/">Retiring Pinafore</a></em>&nbsp;(<a href="/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/">cache</a>)</cite></p>
 </blockquote>
 <p>«&nbsp;<span lang=en>Move fast and outdate things.</span>&nbsp;» n’est pas un <em>motto</em> mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son <a href="https://www.baldurbjarnason.com/">site</a>, son <a href="https://softwarecrisis.baldurbjarnason.com/">livre</a> ou sa <a href="https://softwarecrisis.dev/">newsletter</a>.</p>
 <p>Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique&nbsp;notamment.</p>
 <p>2023, l’année de la maturité&nbsp;😂.</p>

 <blockquote lang="en">
 <p>The symptoms of pop&nbsp;culture:</p>
 <ul>
 <li>A “disdain for history”. Pop cultures believe history doesn’t have anything to teach&nbsp;them.</li>
 <li>Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently&nbsp;inferior.</li>
 <li><mark>What’s next is going to be superior to what’s now.</mark> Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in&nbsp;progress.</li>
 <li>The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be&nbsp;right.</li>
 </ul>
 <p>These traits are deeply irrational but they are the tech industry’s default mode of&nbsp;operation.</p>
 <p><cite><em><a href="https://softwarecrisis.dev/letters/tech-is-a-pop-culture/">Tech Companies Are Irrational Pop Cultures</a></em>&nbsp;(<a href="/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/">cache</a>)</cite></p>
 </blockquote>
 <hr />

 <blockquote lang="en">
 <p>We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. <mark>A dependency you use breaks when one of its dependencies stops working,</mark> leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned&nbsp;around.</p>
 <p>All of which is bad enough but also misses the&nbsp;point.</p>
 <p><cite><em><a href="https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/">The Open-Source Software bubble that is and the blogging bubble that was</a></em>&nbsp;(<a href="/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/">cache</a>)</cite></p>
 </blockquote>

 <blockquote>
 <p>This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), <mark>that’s a pretty small slice of a much larger&nbsp;community.</mark></p>
 <p>We seem to live in different&nbsp;worlds.</p>
 <p><cite><em><a href="https://www.zachleat.com/web/javascript-community/">JavaScript, Community</a></em>&nbsp;(<a href="/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/">cache</a>)</cite></p>
 </blockquote>

    

  
    <h2><a href="/david/2023/01/10/" title="Lien permanent vers cet article">Qualité</a> (2023-01-10)</h2>
    
      
@@ -153,7 +193,9 @@
  
    <h2><a href="/david/2023/01/05/" title="Lien permanent vers cet article">Instanseul</a> (2023-01-05)</h2>
    
      
      <details>
        <summary>Déplier pour lire le contenu de la publication</summary>
        

 <blockquote>
 <p>Peut-être que la centralisation d’une identité mastodon est une hérésie. 🤔</p>
@@ -230,6 +272,7 @@
 <p><cite><em><a href="https://escapingtech.com/tech/opinions/i-was-wrong-about-mastodon-moderation.html">I Was Wrong About Mastodon</a></em>&nbsp;(<a href="/david/cache/2023/daa39b64681b0574bbe189e80c8a4653/">cache</a>)</cite></p>
 </blockquote>

      </details>
    

  
--- a/david/index.html
+++ b/david/index.html
@@ -76,6 +76,7 @@

 <nav>
  <p>
    <a href="/david/2023/01/14/">Dépendances</a>, 
    <a href="/david/2023/01/13/">Eaux&nbsp;grises</a>, 
    <a href="/david/2023/01/12/">Masque</a>, 
    <a href="/david/2023/01/11/">Suspendu</a>, 
@@ -106,18 +107,18 @@
    <a href="/david/2023/don/">#don (1)</a>, 
    <a href="/david/2023/eau/">#eau (1)</a>, 
    <a href="/david/2023/gafam/">#gafam (1)</a>, 
    <a href="/david/2023/gratitude/">#gratitude (1)</a>, 
    <a href="/david/2023/gratitude/">#gratitude (2)</a>, 
    <a href="/david/2023/masque/">#masque (1)</a>, 
    <a href="/david/2023/mastodon/">#mastodon (1)</a>, 
    <a href="/david/2023/partage/">#partage (1)</a>, 
    <a href="/david/2023/photographie/">#photographie (1)</a>, 
    <a href="/david/2023/propriete/">#propriété (1)</a>, 
    <a href="/david/2023/qualite/">#qualité (1)</a>, 
    <a href="/david/2023/recherche/">#recherche (4)</a>, 
    <a href="/david/2023/recherche/">#recherche (5)</a>, 
    <a href="/david/2023/recyclage/">#recyclage (1)</a>, 
    <a href="/david/2023/reponse/">#réponse (2)</a>, 
    <a href="/david/2023/sport/">#sport (2)</a>, 
    <a href="/david/2023/technique/">#technique (3)</a>, 
    <a href="/david/2023/technique/">#technique (4)</a>, 
    <a href="/david/2023/traces/">#traces (1)</a>, 
    <a href="/david/2023/web/">#web (1)</a>.
    
--- a/david/log/index.xml
+++ b/david/log/index.xml
@@ -6,13 +6,55 @@
    <link href="https://larlet.fr/david/" rel="alternate" type="text/html" />
    <link href="https://larlet.fr/david/log/" rel="self" />
    <id>https://larlet.fr/david/</id>
    <updated>2023-01-13T12:00:00+01:00</updated>
    <updated>2023-01-14T12:00:00+01:00</updated>
    <author>
        <name>David Larlet</name>
        <uri>https://larlet.fr/david/</uri>
    </author>
    <rights>Copyright (c) 2004-2023, David Larlet</rights>
    
        <entry xml:lang="fr">
            <title type="html">Dépendances</title>
            <link href="https://larlet.fr/david/2023/01/14/" rel="alternate" type="text/html" />
            <updated>2023-01-14T12:00:00+01:00</updated>
            <id>https://larlet.fr/david/2023/01/14/</id>
            <summary type="html">

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper – both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn’t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore’s tech stack is investing in a dead framework, so &lt;mark&gt;it’s not very attractive for new&amp;nbsp;maintainers.&lt;/mark&gt;&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://nolanlawson.com/2023/01/09/retiring-pinafore/&quot;&gt;Retiring Pinafore&lt;/a&gt;&lt;/em&gt;&amp;nbsp;(&lt;a href=&quot;https://larlet.fr/david/cache/2023/b5acd8bbf209345ff300ea8c10c44181/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;«&amp;nbsp;&lt;span lang=en&gt;Move fast and outdate things.&lt;/span&gt;&amp;nbsp;» n’est pas un &lt;em&gt;motto&lt;/em&gt; mais une constatation. Je suis assez assidu des écrits de Baldur Bjarnason à ce sujet, que ce soit à travers son &lt;a href=&quot;https://www.baldurbjarnason.com/&quot;&gt;site&lt;/a&gt;, son &lt;a href=&quot;https://softwarecrisis.baldurbjarnason.com/&quot;&gt;livre&lt;/a&gt; ou sa &lt;a href=&quot;https://softwarecrisis.dev/&quot;&gt;newsletter&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Je crois que je commence à dépasser la sidération et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexité et cette vitesse que l’on s’impose, avec une composante historique&amp;nbsp;notamment.&lt;/p&gt;
 &lt;p&gt;2023, l’année de la maturité&amp;nbsp;😂.&lt;/p&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;The symptoms of pop&amp;nbsp;culture:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;A “disdain for history”. Pop cultures believe history doesn’t have anything to teach&amp;nbsp;them.&lt;/li&gt;
 &lt;li&gt;Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently&amp;nbsp;inferior.&lt;/li&gt;
 &lt;li&gt;&lt;mark&gt;What’s next is going to be superior to what’s now.&lt;/mark&gt; Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in&amp;nbsp;progress.&lt;/li&gt;
 &lt;li&gt;The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be&amp;nbsp;right.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;These traits are deeply irrational but they are the tech industry’s default mode of&amp;nbsp;operation.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://softwarecrisis.dev/letters/tech-is-a-pop-culture/&quot;&gt;Tech Companies Are Irrational Pop Cultures&lt;/a&gt;&lt;/em&gt;&amp;nbsp;(&lt;a href=&quot;https://larlet.fr/david/cache/2023/45c1becce6fcd8254f2c99fbc1397018/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;hr /&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;We’re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. &lt;mark&gt;A dependency you use breaks when one of its dependencies stops working,&lt;/mark&gt; leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned&amp;nbsp;around.&lt;/p&gt;
 &lt;p&gt;All of which is bad enough but also misses the&amp;nbsp;point.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://www.baldurbjarnason.com/2021/the-oss-bubble-and-the-blogging-bubble/&quot;&gt;The Open-Source Software bubble that is and the blogging bubble that was&lt;/a&gt;&lt;/em&gt;&amp;nbsp;(&lt;a href=&quot;https://larlet.fr/david/cache/2023/d6b891fd250a6ae967ae55564770b67a/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;

 &lt;blockquote&gt;
 &lt;p&gt;This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), &lt;mark&gt;that’s a pretty small slice of a much larger&amp;nbsp;community.&lt;/mark&gt;&lt;/p&gt;
 &lt;p&gt;We seem to live in different&amp;nbsp;worlds.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://www.zachleat.com/web/javascript-community/&quot;&gt;JavaScript, Community&lt;/a&gt;&lt;/em&gt;&amp;nbsp;(&lt;a href=&quot;https://larlet.fr/david/cache/2023/7ff62009f21336b8eb54ea18261bcfb7/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;nav&gt;&lt;p&gt;&lt;a href=&quot;https://larlet.fr/david/2023/gratitude/&quot;&gt;#gratitude&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2023/recherche/&quot;&gt;#recherche&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2023/technique/&quot;&gt;#technique&lt;/a&gt;&lt;/p&gt;&lt;/nav&gt;&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
        </entry>
    
        <entry xml:lang="fr">
            <title type="html">Eaux&amp;nbsp;grises</title>
            <link href="https://larlet.fr/david/2023/01/13/" rel="alternate" type="text/html" />
--- a/david/recherche/index.html
+++ b/david/recherche/index.html
@@ -231,6 +231,12 @@
 </template>
 <script id="search-index" type="application/json">
  [
  {
    "title": "D\u00e9pendances",
    "url": "/david/2023/01/14/",
    "date": "2023-01-14",
    "content": "I suspect one of the reasons for this is that Pinafore is written in Svelte v2 and Sapper \u2013 both of which are deprecated in favor of Svelte v3 and SvelteKit. Not only is there no migration path from Svelte v2 to v3, but there isn\u2019t one from Sapper to SvelteKit either. (And on top of that, I had to fork Sapper pretty heavily.) Anyone making a bet on learning Pinafore\u2019s tech stack is investing in a dead framework, so it\u2019s not very attractive for new\u00a0maintainers. Retiring Pinafore  \u00ab\u00a0Move fast and outdate things.\u00a0\u00bb n\u2019est pas un motto mais une constatation. Je suis assez assidu des \u00e9crits de Baldur Bjarnason \u00e0 ce sujet, que ce soit \u00e0 travers son site, son livre ou sa newsletter. Je crois que je commence \u00e0 d\u00e9passer la sid\u00e9ration et le rejet pour tenter de comprendre un peu mieux les raisons profondes de toute cette complexit\u00e9 et cette vitesse que l\u2019on s\u2019impose, avec une composante historique\u00a0notamment. 2023, l\u2019ann\u00e9e de la maturit\u00e9\u00a0\ud83d\ude02. The symptoms of pop\u00a0culture: A \u201cdisdain for history\u201d. Pop cultures believe history doesn\u2019t have anything to teach\u00a0them. Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently\u00a0inferior. What\u2019s next is going to be superior to what\u2019s now. Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in\u00a0progress. The \u201cPop\u201d in \u201cPop Culture\u201d stands for \u201cpopularity\u201d. If it\u2019s popular then it must be\u00a0right. These traits are deeply irrational but they are the tech industry\u2019s default mode of\u00a0operation. Tech Companies Are Irrational Pop Cultures  We\u2019re starting to see the initial decay hit the parts of the web dev ecosystem that are the furthest away from the cheap money fountains Google and Facebook are providing. Core projects run out of money. Git commits stop. A dependency you use breaks when one of its dependencies stops working, leading somebody to fork it with a quick fix or replacement dependency. Bandaid fixes to decaying OSS projects start to crop up in more and more places. We start to see blog posts saying that all we need to do is get enough people to donate money or pay for support. Everything will be fine. Just look at how OpenSSL got turned\u00a0around. All of which is bad enough but also misses the\u00a0point. The Open-Source Software bubble that is and the blogging bubble that was  This JavaScript community (if judged by the demographics of this survey) seems to be comprised mostly of folks that are largely building with React, webpack, and Jest. With React on 3.2% of web sites and jQuery at 77.7% (as of January 2023), that\u2019s a pretty small slice of a much larger\u00a0community. We seem to live in different\u00a0worlds. JavaScript, Community "
  },
  {
    "title": "Eaux&nbsp;grises",
    "url": "/david/2023/01/13/",