vor 9 Monaten · 521af1e717
--- a/david/2024/02/22/index.html
+++ b/david/2024/02/22/index.html
@@ -152,6 +152,10 @@
         title="Aller à la page de recherche"
         rel="search" data-no-instant>Recherche</a>
      
        • <a rel="next"
            href="/david/2024/02/23/"
            title="Publication suivante : Préparatifs">Suivant →</a>
      
    </p>
  </nav>
  
@@ -232,6 +236,10 @@
      
      <a href="/david/2024/" title="Liste des publications récentes">↑ En 2024</a>
      
        • <a rel="next"
            href="/david/2024/02/23/"
            title="Publication suivante : Préparatifs">Suivant →</a>
      
    </p>
  </nav>

--- a/david/2024/02/23/index.html
+++ b/david/2024/02/23/index.html
@@ -0,0 +1,434 @@
 <!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>
    Préparatifs
  — David Larlet</title>
  <meta name="description" content="J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon certaine.">
  <!-- 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)">
  <!-- Is that even respected? Retrospectively? What a shAItshow…
  https://neil-clarke.com/block-the-bots-that-feed-ai-models-by-scraping-your-website/ -->
  <meta name="robots" content="noai, noimageai">
  <!-- Documented, feel free to shoot an email. -->
  <link rel="stylesheet" href="/static/david/css/style_2024-02-03.css">
  <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  <link rel="preload"
        href="/static/david/css/fonts/century_supra_ot_a_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/century_supra_ot_a_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/century_supra_ot_a_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/century_supra_ot_b_regular.woff2"
        as="font"
        type="font/woff2"
        media="(prefers-color-scheme: dark)"
        crossorigin>
  <link rel="preload"
        href="/static/david/css/fonts/century_supra_ot_b_bold.woff2"
        as="font"
        type="font/woff2"
        media="(prefers-color-scheme: dark)"
        crossorigin>
  <link rel="preload"
        href="/static/david/css/fonts/century_supra_ot_b_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>
  
 <style type="text/css">
  .tippy-content {
    min-width: 280px;
    padding: .5rem;
    font-size: calc(var(--fluid-0) * 0.8);
    font-family: var(--labor-font);
    letter-spacing: initial;
    text-align: left;
  }
  .tippy-content h3 {
    margin-top: 0;
  }
  .tippy-content h3 img {
    max-width: 2rem;
    max-height: 2rem;
    display: inline-block;
  }
  .tippy-content .tippy-links {
    display: flex;
    justify-content: space-around;
  }
  .tippy-content a {
    padding: .4rem;
    color: #F06048;
  }
 </style>

  <body data-instant-intensity="viewport-all">
    <article>
      
  <header>
    <hgroup>
      <h1>Préparatifs</h1>
      <p>Le <time datetime="2024-02-23">23 février 2024</time></p>
    </hgroup>
  </header>
  <nav>
    <p>
      
        <a rel="prev"
           href="/david/2024/02/22/"
           title="Publication précédente : Responsabilité">← Précédent</a> •
      
      <a href="/david/" title="Aller à l’accueil" rel="up">Accueil</a>
      •
      <a href="/david/recherche/"
         title="Aller à la page de recherche"
         rel="search" data-no-instant>Recherche</a>
      
    </p>
  </nav>
  
 <p>J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon&nbsp;certaine.</p>
 <a href="#hr-86" title="Lien vers cette section de la page"><hr id="hr-86" /></a>

 <blockquote lang="en">
 <p>A utopia for web that I can envision would have <mark>rich component creation</mark> and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge&nbsp;amounts.</p>
 <p><cite><em><a data-link-domain="codeburst.io" href="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e" hreflang="en"
            title="Consultation de l’article (anglais)">Generating Config driven Dynamic Forms using Web Components</a>
            <a href="/david/cache/2024/5da390fa8d93278cd62233d3915729e7/" hreflang="en"
                data-tippy data-description="Over the years, we as UI Developers have become so habitual of using the already available UI Frameworks and Libraries like React, Angular, Vue etc due to the increasing demand of shipping things…"
                data-source="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e"
                data-date="2024-02-23"
                data-favicon="https://miro.medium.com/v2/resize:fill:256:256/1*mNmxddJJTzkiBfK77mWuGA.png"
                data-domain="codeburst.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des <em>Web Components</em>. Cet article de 2019&nbsp;donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi <a data-link-domain="dev.to" href="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj" hreflang="en"
            title="Consultation de l’article (anglais)">cet autre article</a>
            <a href="/david/cache/2024/2cadf792810f64540605c86a1431cb6b/" hreflang="en"
                data-tippy data-description="The ElementInternals API allows us to create form-associated custom elements which we can use to make our own supercharged form fields."
                data-source="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj"
                data-date="2024-02-23"
                data-favicon="https://media.dev.to/cdn-cgi/image/width=192,height=,fit=scale-down,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8j7kvp660rqzt99zui8e.png"
                data-domain="dev.to"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> qui m’a permis de découvrir <a data-link-domain="MDN" href="https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals">ElementInternals</a>. Des frameworks comme Shoelace <a data-link-domain="shoelace.style" href="https://shoelace.style/getting-started/form-controls">pourraient être inspirants</a> dans le&nbsp;domaine.</p>
 <a href="#hr-87" title="Lien vers cette section de la page"><hr id="hr-87" /></a>

 <blockquote lang="en">
 <p>RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2&nbsp;got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a <em>huge</em> boost. Debian adopted GNOME 3&nbsp;and systemd, annoying lots of its developers and causing the Devuan fork to&nbsp;happen.</p>
 <p><cite><em><a data-link-domain="liam-on-linux.dreamwidth.org" href="https://liam-on-linux.dreamwidth.org/85359.html" hreflang="en"
            title="Consultation de l’article (anglais)">Everyone seems to forget why GNOME and GNOME 3&nbsp;and Unity happened</a>
            <a href="/david/cache/2024/ecae6fcce7e86066e432b5f38b2299ca/" hreflang="en"
                data-tippy data-description="That is *what* it came from, yes, but not *why*."
                data-source="https://liam-on-linux.dreamwidth.org/85359.html"
                data-date="2024-02-23"
                data-favicon="https://liam-on-linux.dreamwidth.org/favicon.ico"
                data-domain="liam-on-linux.dreamwidth.org"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Fascinante&nbsp;histoire.</p>
 <a href="#hr-88" title="Lien vers cette section de la page"><hr id="hr-88" /></a>

 <blockquote lang="en">
 <p>As of version 2.1.0&nbsp;this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these&nbsp;features.</p>
 <p><cite><em><a data-link-domain="github.com" href="https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0">Release notes de Plausible&nbsp;2.1.0</a></em></cite></p>
 </blockquote>
 <p>Des <a data-link-domain="plausible.io" href="https://plausible.io/blog/community-edition" hreflang="en"
            title="Consultation de l’article (anglais)">raisons un peu plus détaillées</a>
            <a href="/david/cache/2024/d6e0a9beec0623cc66cede135fc7acdc/" hreflang="en"
                data-tippy data-description="We’re introducing the “free as in beer”, self-hosted and AGPL-licensed Plausible Community Edition (CE)."
                data-source="https://plausible.io/blog/community-edition"
                data-date="2024-02-23"
                data-favicon="https://plausible.io/assets/images/icon/favicon-16x16.png"
                data-domain="plausible.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> ayant motivé ce&nbsp;choix.</p>

  
    <nav>
      <p>
        
          <a href="/david/2024/apprentissage/"
             title="Liste de tous les articles 2024 associés à cette étiquette"
             rel="tag">#apprentissage</a>
        
          <a href="/david/2024/processus/"
             title="Liste de tous les articles 2024 associés à cette étiquette"
             rel="tag">#processus</a>
        
          <a href="/david/2024/web/"
             title="Liste de tous les articles 2024 associés à cette étiquette"
             rel="tag">#web</a>
        
        <a href="/david/2024/#tags" title="Liste de toutes les étiquettes 2024">tous ?</a>
      </p>
    </nav>
  
  <nav>
    <p>
      
        <a rel="prev"
           href="/david/2024/02/22/"
           title="Publication précédente : Responsabilité">← Précédent</a> •
      
      <a href="/david/2024/" title="Liste des publications récentes">↑ En 2024</a>
      
    </p>
  </nav>

      
        <form action="/david/recherche/" method="get">
          <fieldset>
            <legend>Recherche</legend>
            <label for="input-search">Termes de votre recherche :</label>
            <input id="input-search" type="search" name="s" aria-describedby="indexation-infos" required>
            <input type="submit" value="Chercher">
            <p id="indexation-infos">
              <small>
                Seuls les contenus de ces 8 dernières années sont indexés.
              </small>
            </p>
          </fieldset>
        </form>
      
      <aside>
        <theme-toggle></theme-toggle>
      </aside>
    </article>
    <hr>
    <footer>
      <p>
        <a href="/david/" title="Aller à l’accueil">Accueil</a>
        •
        <a href="/david/log/" title="Accès au flux RSS">Suivre</a>
        •
        <a href="http://larlet.com"
           title="Go to my English profile"
           data-instant>Pro</a>
        •
        <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">Email</a>
        •
        <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">Légal</abbr>
      </p>
      <template id="theme-selector">
        <form>
          <style type="text/css">
            fieldset div {
              text-align: center;
            }
          </style>
          <fieldset>
            <legend>Thème</legend>
            <div>
              <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>
            </div>
          </fieldset>
        </form>
      </template>
    </footer>
    <script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
    <script>
      class ThemeToggle extends HTMLElement {
        constructor() {
          super()
          const themeSelectorTemplate = document.querySelector('#theme-selector')
          const form = themeSelectorTemplate.content.firstElementChild
          this.attachShadow({ mode: 'open' })
          this.shadowRoot.appendChild(form.cloneNode(true))
        }

        connectedCallback() {
          const form = this.shadowRoot.querySelector('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 colorsLayer = undefined
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
          let mediaRules = []
          for (const layerRule of styleSheet.cssRules) {
            if (!(layerRule instanceof CSSLayerBlockRule)) {
              continue
            }
            if (layerRule.name === 'colors') {
              colorsLayer = layerRule
            }
            for (const cssRule of layerRule.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) {
            // Safari requires the `0` second parameter (even if default).
            colorsLayer.insertRule(mediaRule.cssText, 0)
            hasDarkRules = true
          }
        }

        if (hasDarkRules) {
          if ('customElements' in window && !customElements.get('theme-toggle')) {
            customElements.define('theme-toggle', ThemeToggle)
          }
        }
      })
    </script>
    
  <script src="/static/david/js/popper-2.11.8.min.js"></script>
  <script src="/static/david/js/tippy-bundle-6.3.7.umd.min.js"></script>
  <script>
    tippy('[data-tippy]', {
      content(reference) {
        reference.addEventListener('click', (e) => e.preventDefault())
        return `
        <h3 lang="fr">
          <img src="${reference.dataset.favicon}" loading="lazy">
          <a href="${reference.dataset.source}"
            >Article sur ${reference.dataset.domain}</a></h3>
        <p lang="${reference.hreflang}"><em>${reference.dataset.description}</em></p>
        <div class="tippy-links" lang="fr">
          <a href="${reference.href}">Archive au ${reference.dataset.date}</a>
        </div>
        `
      },
      allowHTML: true,
      interactive: true,
      delay: [150, 700],
      hideOnClick: false
    })
  </script>

  </body>
 </html>
--- a/david/2024/_sources/2024-02-23
+++ b/david/2024/_sources/2024-02-23
@@ -0,0 +1,29 @@
 # Préparatifs

 J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon certaine.

 ---

 > [en] A utopia for web that I can envision would have ==rich component creation== and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge amounts.
 > 
 > <cite>*[Generating Config driven Dynamic Forms using Web Components](https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e)*</cite>

 Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des *Web Components*. Cet article de 2019 donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi [cet autre article](https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj) qui m’a permis de découvrir [ElementInternals](https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals). Des frameworks comme Shoelace [pourraient être inspirants](https://shoelace.style/getting-started/form-controls) dans le domaine.

 ---

 > [en] RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2 got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a *huge* boost. Debian adopted GNOME 3 and systemd, annoying lots of its developers and causing the Devuan fork to happen.
 > 
 > <cite>*[Everyone seems to forget why GNOME and GNOME 3 and Unity happened](https://liam-on-linux.dreamwidth.org/85359.html)*</cite>

 Fascinante histoire.

 ---

 > [en] As of version 2.1.0 this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these features.
 > 
 > <cite>*[Release notes de Plausible 2.1.0](https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0)*</cite>

 Des [raisons un peu plus détaillées](https://plausible.io/blog/community-edition) ayant motivé ce choix.

 #apprentissage #processus #web
--- a/david/2024/apprentissage/index.html
+++ b/david/2024/apprentissage/index.html
@@ -134,6 +134,114 @@
    </p>
  </nav>
  
    <h2>
      <a href="/david/2024/02/23/" title="Lien permanent vers cet article">Préparatifs</a> <time datetime="2024-02-23">23 février 2024</time>
    </h2>
    
 <p>J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon&nbsp;certaine.</p>
 <a href="#hr-86" title="Lien vers cette section de la page"><hr id="hr-86" /></a>

 <blockquote lang="en">
 <p>A utopia for web that I can envision would have <mark>rich component creation</mark> and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge&nbsp;amounts.</p>
 <p><cite><em><a data-link-domain="codeburst.io" href="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e" hreflang="en"
            title="Consultation de l’article (anglais)">Generating Config driven Dynamic Forms using Web Components</a>
            <a href="/david/cache/2024/5da390fa8d93278cd62233d3915729e7/" hreflang="en"
                data-tippy data-description="Over the years, we as UI Developers have become so habitual of using the already available UI Frameworks and Libraries like React, Angular, Vue etc due to the increasing demand of shipping things…"
                data-source="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e"
                data-date="2024-02-23"
                data-favicon="https://miro.medium.com/v2/resize:fill:256:256/1*mNmxddJJTzkiBfK77mWuGA.png"
                data-domain="codeburst.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des <em>Web Components</em>. Cet article de 2019&nbsp;donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi <a data-link-domain="dev.to" href="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj" hreflang="en"
            title="Consultation de l’article (anglais)">cet autre article</a>
            <a href="/david/cache/2024/2cadf792810f64540605c86a1431cb6b/" hreflang="en"
                data-tippy data-description="The ElementInternals API allows us to create form-associated custom elements which we can use to make our own supercharged form fields."
                data-source="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj"
                data-date="2024-02-23"
                data-favicon="https://media.dev.to/cdn-cgi/image/width=192,height=,fit=scale-down,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8j7kvp660rqzt99zui8e.png"
                data-domain="dev.to"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> qui m’a permis de découvrir <a data-link-domain="MDN" href="https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals">ElementInternals</a>. Des frameworks comme Shoelace <a data-link-domain="shoelace.style" href="https://shoelace.style/getting-started/form-controls">pourraient être inspirants</a> dans le&nbsp;domaine.</p>
 <a href="#hr-87" title="Lien vers cette section de la page"><hr id="hr-87" /></a>

 <blockquote lang="en">
 <p>RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2&nbsp;got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a <em>huge</em> boost. Debian adopted GNOME 3&nbsp;and systemd, annoying lots of its developers and causing the Devuan fork to&nbsp;happen.</p>
 <p><cite><em><a data-link-domain="liam-on-linux.dreamwidth.org" href="https://liam-on-linux.dreamwidth.org/85359.html" hreflang="en"
            title="Consultation de l’article (anglais)">Everyone seems to forget why GNOME and GNOME 3&nbsp;and Unity happened</a>
            <a href="/david/cache/2024/ecae6fcce7e86066e432b5f38b2299ca/" hreflang="en"
                data-tippy data-description="That is *what* it came from, yes, but not *why*."
                data-source="https://liam-on-linux.dreamwidth.org/85359.html"
                data-date="2024-02-23"
                data-favicon="https://liam-on-linux.dreamwidth.org/favicon.ico"
                data-domain="liam-on-linux.dreamwidth.org"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Fascinante&nbsp;histoire.</p>
 <a href="#hr-88" title="Lien vers cette section de la page"><hr id="hr-88" /></a>

 <blockquote lang="en">
 <p>As of version 2.1.0&nbsp;this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these&nbsp;features.</p>
 <p><cite><em><a data-link-domain="github.com" href="https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0">Release notes de Plausible&nbsp;2.1.0</a></em></cite></p>
 </blockquote>
 <p>Des <a data-link-domain="plausible.io" href="https://plausible.io/blog/community-edition" hreflang="en"
            title="Consultation de l’article (anglais)">raisons un peu plus détaillées</a>
            <a href="/david/cache/2024/d6e0a9beec0623cc66cede135fc7acdc/" hreflang="en"
                data-tippy data-description="We’re introducing the “free as in beer”, self-hosted and AGPL-licensed Plausible Community Edition (CE)."
                data-source="https://plausible.io/blog/community-edition"
                data-date="2024-02-23"
                data-favicon="https://plausible.io/assets/images/icon/favicon-16x16.png"
                data-domain="plausible.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> ayant motivé ce&nbsp;choix.</p>

    
      <nav>
        <p>
          
            <a href="/david/2024/apprentissage/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#apprentissage</a>
          
            <a href="/david/2024/processus/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#processus</a>
          
            <a href="/david/2024/web/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#web</a>
          
          <a href="/david/2024/#tags" title="Liste de toutes les étiquettes 2024">tous ?</a>
        </p>
      </nav>
    
  
    <h2>
      <a href="/david/2024/02/19/" title="Lien permanent vers cet article">Injection</a> <time datetime="2024-02-19">19 février 2024</time>
    </h2>
--- a/david/2024/index.html
+++ b/david/2024/index.html
@@ -186,7 +186,8 @@
      <a href="/david/2024/02/19/">Injection</a>, 
      <a href="/david/2024/02/20/">Véhicule</a>, 
      <a href="/david/2024/02/21/">Cinéma</a>, 
      <a href="/david/2024/02/22/">Responsabilité</a>.
      <a href="/david/2024/02/22/">Responsabilité</a>, 
      <a href="/david/2024/02/23/">Préparatifs</a>.
      
    </p>
  
@@ -196,7 +197,7 @@
      <a href="/david/2024/accessibilite/" rel="tag">#accessibilité (3)</a>, 
      <a href="/david/2024/accompagnement/" rel="tag">#accompagnement (2)</a>, 
      <a href="/david/2024/addiction/" rel="tag">#addiction (4)</a>, 
      <a href="/david/2024/apprentissage/" rel="tag">#apprentissage (12)</a>, 
      <a href="/david/2024/apprentissage/" rel="tag">#apprentissage (13)</a>, 
      <a href="/david/2024/commun/" rel="tag">#commun (7)</a>, 
      <a href="/david/2024/communaute/" rel="tag">#communauté (5)</a>, 
      <a href="/david/2024/decision/" rel="tag">#décision (7)</a>, 
@@ -220,14 +221,14 @@
      <a href="/david/2024/partage/" rel="tag">#partage (3)</a>, 
      <a href="/david/2024/parvenir/" rel="tag">#parvenir (1)</a>, 
      <a href="/david/2024/photographie/" rel="tag">#photographie (2)</a>, 
      <a href="/david/2024/processus/" rel="tag">#processus (8)</a>, 
      <a href="/david/2024/processus/" rel="tag">#processus (9)</a>, 
      <a href="/david/2024/protopie/" rel="tag">#protopie (6)</a>, 
      <a href="/david/2024/psychologie/" rel="tag">#psychologie (6)</a>, 
      <a href="/david/2024/solastalgia/" rel="tag">#solastalgia (1)</a>, 
      <a href="/david/2024/sport/" rel="tag">#sport (3)</a>, 
      <a href="/david/2024/technique/" rel="tag">#technique (12)</a>, 
      <a href="/david/2024/velo/" rel="tag">#vélo (1)</a>, 
      <a href="/david/2024/web/" rel="tag">#web (7)</a>.
      <a href="/david/2024/web/" rel="tag">#web (8)</a>.
      
    </p>
  
--- a/david/2024/processus/index.html
+++ b/david/2024/processus/index.html
@@ -134,6 +134,114 @@
    </p>
  </nav>
  
    <h2>
      <a href="/david/2024/02/23/" title="Lien permanent vers cet article">Préparatifs</a> <time datetime="2024-02-23">23 février 2024</time>
    </h2>
    
 <p>J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon&nbsp;certaine.</p>
 <a href="#hr-86" title="Lien vers cette section de la page"><hr id="hr-86" /></a>

 <blockquote lang="en">
 <p>A utopia for web that I can envision would have <mark>rich component creation</mark> and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge&nbsp;amounts.</p>
 <p><cite><em><a data-link-domain="codeburst.io" href="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e" hreflang="en"
            title="Consultation de l’article (anglais)">Generating Config driven Dynamic Forms using Web Components</a>
            <a href="/david/cache/2024/5da390fa8d93278cd62233d3915729e7/" hreflang="en"
                data-tippy data-description="Over the years, we as UI Developers have become so habitual of using the already available UI Frameworks and Libraries like React, Angular, Vue etc due to the increasing demand of shipping things…"
                data-source="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e"
                data-date="2024-02-23"
                data-favicon="https://miro.medium.com/v2/resize:fill:256:256/1*mNmxddJJTzkiBfK77mWuGA.png"
                data-domain="codeburst.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des <em>Web Components</em>. Cet article de 2019&nbsp;donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi <a data-link-domain="dev.to" href="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj" hreflang="en"
            title="Consultation de l’article (anglais)">cet autre article</a>
            <a href="/david/cache/2024/2cadf792810f64540605c86a1431cb6b/" hreflang="en"
                data-tippy data-description="The ElementInternals API allows us to create form-associated custom elements which we can use to make our own supercharged form fields."
                data-source="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj"
                data-date="2024-02-23"
                data-favicon="https://media.dev.to/cdn-cgi/image/width=192,height=,fit=scale-down,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8j7kvp660rqzt99zui8e.png"
                data-domain="dev.to"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> qui m’a permis de découvrir <a data-link-domain="MDN" href="https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals">ElementInternals</a>. Des frameworks comme Shoelace <a data-link-domain="shoelace.style" href="https://shoelace.style/getting-started/form-controls">pourraient être inspirants</a> dans le&nbsp;domaine.</p>
 <a href="#hr-87" title="Lien vers cette section de la page"><hr id="hr-87" /></a>

 <blockquote lang="en">
 <p>RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2&nbsp;got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a <em>huge</em> boost. Debian adopted GNOME 3&nbsp;and systemd, annoying lots of its developers and causing the Devuan fork to&nbsp;happen.</p>
 <p><cite><em><a data-link-domain="liam-on-linux.dreamwidth.org" href="https://liam-on-linux.dreamwidth.org/85359.html" hreflang="en"
            title="Consultation de l’article (anglais)">Everyone seems to forget why GNOME and GNOME 3&nbsp;and Unity happened</a>
            <a href="/david/cache/2024/ecae6fcce7e86066e432b5f38b2299ca/" hreflang="en"
                data-tippy data-description="That is *what* it came from, yes, but not *why*."
                data-source="https://liam-on-linux.dreamwidth.org/85359.html"
                data-date="2024-02-23"
                data-favicon="https://liam-on-linux.dreamwidth.org/favicon.ico"
                data-domain="liam-on-linux.dreamwidth.org"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Fascinante&nbsp;histoire.</p>
 <a href="#hr-88" title="Lien vers cette section de la page"><hr id="hr-88" /></a>

 <blockquote lang="en">
 <p>As of version 2.1.0&nbsp;this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these&nbsp;features.</p>
 <p><cite><em><a data-link-domain="github.com" href="https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0">Release notes de Plausible&nbsp;2.1.0</a></em></cite></p>
 </blockquote>
 <p>Des <a data-link-domain="plausible.io" href="https://plausible.io/blog/community-edition" hreflang="en"
            title="Consultation de l’article (anglais)">raisons un peu plus détaillées</a>
            <a href="/david/cache/2024/d6e0a9beec0623cc66cede135fc7acdc/" hreflang="en"
                data-tippy data-description="We’re introducing the “free as in beer”, self-hosted and AGPL-licensed Plausible Community Edition (CE)."
                data-source="https://plausible.io/blog/community-edition"
                data-date="2024-02-23"
                data-favicon="https://plausible.io/assets/images/icon/favicon-16x16.png"
                data-domain="plausible.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> ayant motivé ce&nbsp;choix.</p>

    
      <nav>
        <p>
          
            <a href="/david/2024/apprentissage/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#apprentissage</a>
          
            <a href="/david/2024/processus/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#processus</a>
          
            <a href="/david/2024/web/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#web</a>
          
          <a href="/david/2024/#tags" title="Liste de toutes les étiquettes 2024">tous ?</a>
        </p>
      </nav>
    
  
    <h2>
      <a href="/david/2024/02/13/" title="Lien permanent vers cet article">Feutrage</a> <time datetime="2024-02-13">13 février 2024</time>
    </h2>
--- a/david/2024/web/index.html
+++ b/david/2024/web/index.html
@@ -134,6 +134,114 @@
    </p>
  </nav>
  
    <h2>
      <a href="/david/2024/02/23/" title="Lien permanent vers cet article">Préparatifs</a> <time datetime="2024-02-23">23 février 2024</time>
    </h2>
    
 <p>J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon&nbsp;certaine.</p>
 <a href="#hr-86" title="Lien vers cette section de la page"><hr id="hr-86" /></a>

 <blockquote lang="en">
 <p>A utopia for web that I can envision would have <mark>rich component creation</mark> and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge&nbsp;amounts.</p>
 <p><cite><em><a data-link-domain="codeburst.io" href="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e" hreflang="en"
            title="Consultation de l’article (anglais)">Generating Config driven Dynamic Forms using Web Components</a>
            <a href="/david/cache/2024/5da390fa8d93278cd62233d3915729e7/" hreflang="en"
                data-tippy data-description="Over the years, we as UI Developers have become so habitual of using the already available UI Frameworks and Libraries like React, Angular, Vue etc due to the increasing demand of shipping things…"
                data-source="https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e"
                data-date="2024-02-23"
                data-favicon="https://miro.medium.com/v2/resize:fill:256:256/1*mNmxddJJTzkiBfK77mWuGA.png"
                data-domain="codeburst.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des <em>Web Components</em>. Cet article de 2019&nbsp;donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi <a data-link-domain="dev.to" href="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj" hreflang="en"
            title="Consultation de l’article (anglais)">cet autre article</a>
            <a href="/david/cache/2024/2cadf792810f64540605c86a1431cb6b/" hreflang="en"
                data-tippy data-description="The ElementInternals API allows us to create form-associated custom elements which we can use to make our own supercharged form fields."
                data-source="https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj"
                data-date="2024-02-23"
                data-favicon="https://media.dev.to/cdn-cgi/image/width=192,height=,fit=scale-down,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8j7kvp660rqzt99zui8e.png"
                data-domain="dev.to"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> qui m’a permis de découvrir <a data-link-domain="MDN" href="https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals">ElementInternals</a>. Des frameworks comme Shoelace <a data-link-domain="shoelace.style" href="https://shoelace.style/getting-started/form-controls">pourraient être inspirants</a> dans le&nbsp;domaine.</p>
 <a href="#hr-87" title="Lien vers cette section de la page"><hr id="hr-87" /></a>

 <blockquote lang="en">
 <p>RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2&nbsp;got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a <em>huge</em> boost. Debian adopted GNOME 3&nbsp;and systemd, annoying lots of its developers and causing the Devuan fork to&nbsp;happen.</p>
 <p><cite><em><a data-link-domain="liam-on-linux.dreamwidth.org" href="https://liam-on-linux.dreamwidth.org/85359.html" hreflang="en"
            title="Consultation de l’article (anglais)">Everyone seems to forget why GNOME and GNOME 3&nbsp;and Unity happened</a>
            <a href="/david/cache/2024/ecae6fcce7e86066e432b5f38b2299ca/" hreflang="en"
                data-tippy data-description="That is *what* it came from, yes, but not *why*."
                data-source="https://liam-on-linux.dreamwidth.org/85359.html"
                data-date="2024-02-23"
                data-favicon="https://liam-on-linux.dreamwidth.org/favicon.ico"
                data-domain="liam-on-linux.dreamwidth.org"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a></em></cite></p>
 </blockquote>
 <p>Fascinante&nbsp;histoire.</p>
 <a href="#hr-88" title="Lien vers cette section de la page"><hr id="hr-88" /></a>

 <blockquote lang="en">
 <p>As of version 2.1.0&nbsp;this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these&nbsp;features.</p>
 <p><cite><em><a data-link-domain="github.com" href="https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0">Release notes de Plausible&nbsp;2.1.0</a></em></cite></p>
 </blockquote>
 <p>Des <a data-link-domain="plausible.io" href="https://plausible.io/blog/community-edition" hreflang="en"
            title="Consultation de l’article (anglais)">raisons un peu plus détaillées</a>
            <a href="/david/cache/2024/d6e0a9beec0623cc66cede135fc7acdc/" hreflang="en"
                data-tippy data-description="We’re introducing the “free as in beer”, self-hosted and AGPL-licensed Plausible Community Edition (CE)."
                data-source="https://plausible.io/blog/community-edition"
                data-date="2024-02-23"
                data-favicon="https://plausible.io/assets/images/icon/favicon-16x16.png"
                data-domain="plausible.io"
                ><svg xmlns="http://www.w3.org/2000/svg"
                    width="24" height="24" viewBox="0 0 24 24" fill="none"
                    stroke="currentColor" stroke-width="2" stroke-linecap="square"
                    stroke-linejoin="round"><circle cx="12" cy="12" r="10"></circle>
                    <path d="M9.09 9a3 3 0 0 1 5.83 1c0 2-3 3-3 3"></path>
                    <line x1="12" y1="17" x2="12.01" y2="17"></line>
                </svg>
                <span class="sr-only">[archive]</span></a> ayant motivé ce&nbsp;choix.</p>

    
      <nav>
        <p>
          
            <a href="/david/2024/apprentissage/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#apprentissage</a>
          
            <a href="/david/2024/processus/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#processus</a>
          
            <a href="/david/2024/web/"
               title="Liste de tous les articles 2024 associés à cette étiquette"
               rel="tag">#web</a>
          
          <a href="/david/2024/#tags" title="Liste de toutes les étiquettes 2024">tous ?</a>
        </p>
      </nav>
    
  
    <h2>
      <a href="/david/2024/02/19/" title="Lien permanent vers cet article">Injection</a> <time datetime="2024-02-19">19 février 2024</time>
    </h2>
--- a/david/index.html
+++ b/david/index.html
@@ -143,6 +143,7 @@
  <h2>Publications 2024</h2>
  <p>Liste des publications récentes en ordre anté-chronologique :</p>
  <p>
    <a href="/david/2024/02/23/">Préparatifs</a>,
    <a href="/david/2024/02/22/">Responsabilité</a>,
    <a href="/david/2024/02/21/">Cinéma</a>,
    <a href="/david/2024/02/20/">Véhicule</a>,
@@ -204,7 +205,7 @@
    <a href="/david/2024/accessibilite/" rel="tag">#accessibilité (3)</a>,
    <a href="/david/2024/accompagnement/" rel="tag">#accompagnement (2)</a>,
    <a href="/david/2024/addiction/" rel="tag">#addiction (4)</a>,
    <a href="/david/2024/apprentissage/" rel="tag">#apprentissage (12)</a>,
    <a href="/david/2024/apprentissage/" rel="tag">#apprentissage (13)</a>,
    <a href="/david/2024/commun/" rel="tag">#commun (7)</a>,
    <a href="/david/2024/communaute/" rel="tag">#communauté (5)</a>,
    <a href="/david/2024/decision/" rel="tag">#décision (7)</a>,
@@ -228,14 +229,14 @@
    <a href="/david/2024/partage/" rel="tag">#partage (3)</a>,
    <a href="/david/2024/parvenir/" rel="tag">#parvenir (1)</a>,
    <a href="/david/2024/photographie/" rel="tag">#photographie (2)</a>,
    <a href="/david/2024/processus/" rel="tag">#processus (8)</a>,
    <a href="/david/2024/processus/" rel="tag">#processus (9)</a>,
    <a href="/david/2024/protopie/" rel="tag">#protopie (6)</a>,
    <a href="/david/2024/psychologie/" rel="tag">#psychologie (6)</a>,
    <a href="/david/2024/solastalgia/" rel="tag">#solastalgia (1)</a>,
    <a href="/david/2024/sport/" rel="tag">#sport (3)</a>,
    <a href="/david/2024/technique/" rel="tag">#technique (12)</a>,
    <a href="/david/2024/velo/" rel="tag">#vélo (1)</a>,
    <a href="/david/2024/web/" rel="tag">#web (7)</a>.
    <a href="/david/2024/web/" rel="tag">#web (8)</a>.
      
    
  </p>
--- a/david/log/index.xml
+++ b/david/log/index.xml
@@ -6,13 +6,44 @@
    <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>2024-02-23T12:00:00+01:00</updated>
    <updated>2024-02-24T12:00:00+01:00</updated>
    <author>
        <name>David Larlet</name>
        <uri>https://larlet.fr/david/</uri>
    </author>
    <rights>Copyright (c) 2004-2024, David Larlet</rights>
    
        <entry xml:lang="fr">
            <title type="html">Préparatifs</title>
            <link href="https://larlet.fr/david/2024/02/23/" rel="alternate" type="text/html" />
            <updated>2024-02-23T12:00:00+01:00</updated>
            <id>https://larlet.fr/david/2024/02/23/</id>
            <summary type="html">
 &lt;p&gt;J’admire les personnes qui arrivent à prendre une photo de leur sac de manière éclatée avant de partir. J’ai toujours pas mal de choses à rajouter au dernier moment, j’essaye au moins d’avoir les basiques de façon&amp;nbsp;certaine.&lt;/p&gt;
 &lt;hr /&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;A utopia for web that I can envision would have &lt;mark&gt;rich component creation&lt;/mark&gt; and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won’t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge&amp;nbsp;amounts.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://codeburst.io/generating-config-driven-dynamic-forms-using-web-components-7c8d400f7f2e&quot;&gt;Generating Config driven Dynamic Forms using Web&amp;nbsp;Components&lt;/a&gt;&lt;/em&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;Aujourd’hui, j’ai exploré les façons de faire des formulaires en assemblant des &lt;em&gt;Web Components&lt;/em&gt;. Cet article de 2019&amp;nbsp;donne un bon aperçu de ce qu’il est possible de faire. Il y a aussi &lt;a href=&quot;https://dev.to/stuffbreaker/custom-forms-with-web-components-and-elementinternals-4jaj&quot;&gt;cet autre article&lt;/a&gt; qui m’a permis de découvrir &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals&quot;&gt;ElementInternals&lt;/a&gt;. Des frameworks comme Shoelace &lt;a href=&quot;https://shoelace.style/getting-started/form-controls&quot;&gt;pourraient être inspirants&lt;/a&gt; dans le&amp;nbsp;domaine.&lt;/p&gt;
 &lt;hr /&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2&amp;nbsp;got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a &lt;em&gt;huge&lt;/em&gt; boost. Debian adopted GNOME 3&amp;nbsp;and systemd, annoying lots of its developers and causing the Devuan fork to&amp;nbsp;happen.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://liam-on-linux.dreamwidth.org/85359.html&quot;&gt;Everyone seems to forget why GNOME and GNOME 3&amp;nbsp;and Unity&amp;nbsp;happened&lt;/a&gt;&lt;/em&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;Fascinante&amp;nbsp;histoire.&lt;/p&gt;
 &lt;hr /&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;As of version 2.1.0&amp;nbsp;this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these&amp;nbsp;features.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://github.com/plausible/analytics/releases/tag/v2.1.0-rc.0&quot;&gt;Release notes de Plausible&amp;nbsp;2.1.0&lt;/a&gt;&lt;/em&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;Des &lt;a href=&quot;https://plausible.io/blog/community-edition&quot;&gt;raisons un peu plus détaillées&lt;/a&gt; ayant motivé ce&amp;nbsp;choix.&lt;/p&gt;
 &lt;nav&gt;&lt;p&gt;&lt;a href=&quot;https://larlet.fr/david/2024/apprentissage/&quot;&gt;#apprentissage&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/processus/&quot;&gt;#processus&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/web/&quot;&gt;#web&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">Responsabilité</title>
            <link href="https://larlet.fr/david/2024/02/22/" rel="alternate" type="text/html" />
@@ -1272,39 +1303,4 @@ Des affects, qui constituent la nécessaire force motrice du mouvement que nous
 &lt;nav&gt;&lt;p&gt;&lt;a href=&quot;https://larlet.fr/david/2024/apprentissage/&quot;&gt;#apprentissage&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/equipe/&quot;&gt;#équipe&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/velo/&quot;&gt;#vélo&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">Taille</title>
            <link href="https://larlet.fr/david/2024/01/24/" rel="alternate" type="text/html" />
            <updated>2024-01-24T12:00:00+01:00</updated>
            <id>https://larlet.fr/david/2024/01/24/</id>
            <summary type="html">
 &lt;p&gt;On me demande quelle est la taille souhaitable pour &lt;a href=&quot;http://scopyleft.fr/&quot;&gt;Scopyleft&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Il y a plusieurs réponses / contraintes à&amp;nbsp;cela&amp;nbsp;:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;il faudrait que tout le monde puisse être visible dans notre outil de visio (Whereby à ce&amp;nbsp;jour)&amp;#8239;;&lt;/li&gt;
 &lt;li&gt;il faudrait que chacun·e ait un temps de parole suffisant sur une réunion d’une heure (aujourd’hui, ce serait&amp;nbsp;7&amp;#8239;min&amp;nbsp;30)&amp;#8239;;&lt;/li&gt;
 &lt;li&gt;il faudrait pouvoir avoir des interactions en binôme avec chaque personne sur un rythme&amp;nbsp;hebdomadaire.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;Et surtout, nous n’avons pas de volonté de croître plus que ça. Lorsqu’on veut faire des choses qui dépassent nos capacités, il y a les coopératives&amp;nbsp;amies.&lt;/p&gt;
 &lt;hr /&gt;

 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;Further, if we have learned anything in the last 3&amp;nbsp;years as an industry, it should be to strive for building small, highly efficient teams and avoiding bloated, overstaffed organizations at all costs. Larger teams move slower, create more incidental complexity, and are much more susceptible to the layoffs we’ve all been suffering through. &lt;mark&gt;Engineering leaders would be well served to focus on hiring smaller teams&lt;/mark&gt; and providing them with sufficient time and support to create simple solutions that generate business&amp;nbsp;value.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://blog.testdouble.com/posts/2024-01-24-plea-for-lean/&quot;&gt;Echoing Wirth’s plea for lean&amp;nbsp;software&lt;/a&gt;&lt;/em&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;Tout est&amp;nbsp;dit.&lt;/p&gt;
 &lt;hr /&gt;

 &lt;blockquote&gt;
 &lt;p&gt;La nuit est rassurante&lt;br /&gt;
 tout est perdu&lt;br /&gt;
 plus besoin de chercher&lt;br /&gt;
 nos morceaux éparpillés&lt;br /&gt;
 nous voilà réunis&lt;br /&gt;
 par nos&amp;nbsp;obscurités&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;http://etc-iste.blogspot.com/2024/01/reunuit.html&quot;&gt;Réunuit&lt;/a&gt;&lt;/em&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;nav&gt;&lt;p&gt;&lt;a href=&quot;https://larlet.fr/david/2024/communaute/&quot;&gt;#communauté&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/equipe/&quot;&gt;#équipe&lt;/a&gt; &lt;a href=&quot;https://larlet.fr/david/2024/processus/&quot;&gt;#processus&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>
    
 </feed>
--- a/david/recherche/index.html
+++ b/david/recherche/index.html
@@ -276,6 +276,12 @@
    </template>
    
    <script id="search-index" type="application/json">[
  {
    "title": "Pr\u00e9paratifs",
    "url": "/david/2024/02/23/",
    "date": "2024-02-23",
    "content": "J\u2019admire les personnes qui arrivent \u00e0 prendre une photo de leur sac de mani\u00e8re \u00e9clat\u00e9e avant de partir. J\u2019ai toujours pas mal de choses \u00e0 rajouter au dernier moment, j\u2019essaye au moins d\u2019avoir les basiques de fa\u00e7on\u00a0certaine. A utopia for web that I can envision would have rich component creation and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won\u2019t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge\u00a0amounts. Generating Config driven Dynamic Forms using Web\u00a0Components Aujourd\u2019hui, j\u2019ai explor\u00e9 les fa\u00e7ons de faire des formulaires en assemblant des Web Components. Cet article de 2019\u00a0donne un bon aper\u00e7u de ce qu\u2019il est possible de faire. Il y a aussi cet autre article qui m\u2019a permis de d\u00e9couvrir ElementInternals. Des frameworks comme Shoelace pourraient \u00eatre inspirants dans le\u00a0domaine. RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2\u00a0got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a huge boost. Debian adopted GNOME 3\u00a0and systemd, annoying lots of its developers and causing the Devuan fork to\u00a0happen. Everyone seems to forget why GNOME and GNOME 3\u00a0and Unity\u00a0happened Fascinante\u00a0histoire. As of version 2.1.0\u00a0this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these\u00a0features. Release notes de Plausible\u00a02.1.0 Des raisons un peu plus d\u00e9taill\u00e9es ayant motiv\u00e9 ce\u00a0choix."
  },
  {
    "title": "Responsabilit\u00e9",
    "url": "/david/2024/02/22/",
@@ -594,6 +600,12 @@
    "date": "2024-01-01",
    "content": "33\u202f% de 44\u00a0millions de consommateurs vont faire le Dry January 22\u202f% des consommateurs ont une conso excessive, c\u2019est-\u00e0-dire 10\u00a0verres/semaine max et plus de deux\u00a0verres/jour. Les seniors sont aussi tr\u00e8s touch\u00e9\u00b7es. L\u2019alcool est une drogue.. On peut faire la f\u00eate sans alcool et\u00a0s\u2019\u00e9clater. Quand on arr\u00eate\u00a0: bienfaits sur le foie, la peau, le coeur, etc\u2026 Pb\u00a0: m\u00e9moire, troubles cognitifs, responsable de cancer, pb sommeil, d\u00e9compensation de maladie psy,\u2026 41000\u00a0d\u00e9c\u00e8s par an en\u00a0France. Les cinq sympt\u00f4mes d\u00e9finissent un probl\u00e8me de\u00a0d\u00e9pendance\u00a0: Perte de\u00a0contr\u00f4le Usage\u00a0compulsif Envie\u00a0r\u00e9pressive Usage\u00a0chronique Cons\u00e9quences psychiques, physiques, sociales,\u2026 Bon Dry J. pour celleux qui le font\u202f! Moi j\u2019en\u00a0suis\u202f! @Air@framapiaf.org Dans mon entourage, de plus en plus de personnes que j\u2019estime ne boivent pas d\u2019alcool, de plus en plus de personnes qui vieillissent en deviennent d\u00e9pendantes. Je suis davantage attir\u00e9 par la premi\u00e8re option\u2026 et pas pour un seul\u00a0mois. Je me sens pr\u00eat, on verra bien o\u00f9 cela me\u00a0m\u00e8ne. Grosse envie de reprendre la CSS par ici en ce d\u00e9but d\u2019ann\u00e9e. Avec le dilemme de faire chuter cette motivation si je publie d\u00e8s maintenant avec l\u2019ancienne (qui restera effective sur les anciens articles). Je vais essayer de me\u00a0retenir."
  },
  {
    "title": "Pr\u00e9paratifs",
    "url": "/david/2024/02/23/",
    "date": "2024-02-23",
    "content": "J\u2019admire les personnes qui arrivent \u00e0 prendre une photo de leur sac de mani\u00e8re \u00e9clat\u00e9e avant de partir. J\u2019ai toujours pas mal de choses \u00e0 rajouter au dernier moment, j\u2019essaye au moins d\u2019avoir les basiques de fa\u00e7on\u00a0certaine. A utopia for web that I can envision would have rich component creation and manipulation capabilities in built as a part of spec and browsers implementing them. Hence, we won\u2019t have to include any of the heavy third party libraries which will give faster load times to the users by saving the download costs by a huge\u00a0amounts. Generating Config driven Dynamic Forms using Web\u00a0Components Aujourd\u2019hui, j\u2019ai explor\u00e9 les fa\u00e7ons de faire des formulaires en assemblant des Web Components. Cet article de 2019\u00a0donne un bon aper\u00e7u de ce qu\u2019il est possible de faire. Il y a aussi cet autre article qui m\u2019a permis de d\u00e9couvrir ElementInternals. Des frameworks comme Shoelace pourraient \u00eatre inspirants dans le\u00a0domaine. RH uses GNOME 3. Ubuntu used Unity, alienated a lot of people who only knew how to use Windows-like desktops, and that made Mint a huge success. GNOME 2\u00a0got forked as MATE, and Mint adopted it, helping a lot. Mint also built its own fork of GNOME 3, Cinnamon. Formerly tiny niche desktops like Xfce and LXDE got a huge boost. Debian adopted GNOME 3\u00a0and systemd, annoying lots of its developers and causing the Devuan fork to\u00a0happen. Everyone seems to forget why GNOME and GNOME 3\u00a0and Unity\u00a0happened Fascinante\u00a0histoire. As of version 2.1.0\u00a0this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these\u00a0features. Release notes de Plausible\u00a02.1.0 Des raisons un peu plus d\u00e9taill\u00e9es ayant motiv\u00e9 ce\u00a0choix."
  },
  {
    "title": "Responsabilit\u00e9",
    "url": "/david/2024/02/22/",