<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #js</title>
    <link>/tags/js/</link>
    <description>Recent bookmarks tagged #js</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:44 +0000</lastBuildDate>
    <item>
      <title>HTMLcat — Compact notes on HTML, CSS, and JavaScript</title>
      <link>https://htmlcat.net/</link>
      <description>small, native web tricks worth remembering&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #html #js&lt;/p&gt;</description>
      <pubDate>Sat, 22 Aug 2026 04:47:53 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38699</guid>
      <category>html</category>
      <category>js</category>
    </item>
    <item>
      <title>argyleink/prop-for-that: what JS knows, now CSS knows</title>
      <link>https://github.com/argyleink/prop-for-that</link>
      <description>Sliders, pointer position, element visibility, viewport size, battery, network, sensors — JavaScript can read all of it; CSS can&#39;t. prop-for-that writes that runtime state into --live-* and --const-* custom properties — batched and diffed down to one setProperty per frame — so your CSS can compose and react to it with plain calc() and var().&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #js #nifty #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 20 Jun 2026 17:25:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38591</guid>
      <category>css</category>
      <category>js</category>
      <category>nifty</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/add3d938965024b1b491aafe61ddeb3f.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>The handleEvent() method is the absolute best way to handle events in Web Components | Go Make Things</title>
      <link>https://gomakethings.com/the-handleevent-method-is-the-absolute-best-way-to-handle-events-in-web-components/</link>
      <description>A bunch of people shared their own approaches, but the one that absolutely blew my mind was the handleEvent() method, a platform-native method for managing all of the events on your Web Component.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #customelements #js #web #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 19 Dec 2025 01:04:04 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38129</guid>
      <category>customelements</category>
      <category>js</category>
      <category>web</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/bd4be4654582fd450804cdeb64319352.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Please Just Fucking Try HTMX</title>
      <link>https://pleasejusttryhtmx.com/</link>
      <description>Look. I&#39;m not going to call you a fucking moron every other sentence. That&#39;s been done. It&#39;s a whole genre now. And honestly? HTMX doesn&#39;t need me to scream at you to make its point.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #html #htmx #js #react #web #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 19 Dec 2025 00:24:44 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38122</guid>
      <category>html</category>
      <category>htmx</category>
      <category>js</category>
      <category>react</category>
      <category>web</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The Web Platform is a Triumph of Object-Oriented Programming | That HTML Blog</title>
      <link>https://thathtml.blog/2025/12/the-dom-is-a-triumph-of-object-oriented-programming/</link>
      <description>It’s not just that web APIs often take advantage of OOP. They would not exist without OOP! Virtually every web API you have ever used is designed specifically within the OOP paradigm. And every entity in the lifecycle of a web page is based on objects. These objects are instances of classes and in a great many cases these classes are subclasses of other classes. This means that key functionality is spread across a class hierarchy. That isn’t a bug, it’s a feature! And this means that it’s absurd to think that to write a web app you need to reach for a “framework”. The Web Platform is a framework.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dom #html #js #web #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 18 Dec 2025 21:01:09 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38120</guid>
      <category>dom</category>
      <category>html</category>
      <category>js</category>
      <category>web</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/cb7bc3e7c278969298fe11b11c73404a.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Why use React? | Clearleft</title>
      <link>https://clearleft.com/thinking/why-use-react</link>
      <description>This isn’t a rhetorical question. I genuinely want to know why developers choose to build websites using React.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #react #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 28 Nov 2025 01:13:03 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38035</guid>
      <category>js</category>
      <category>react</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/0bf5656745ab0338dea5fb89186b2dd7.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Lea Verou, PhD: &#34;The #JS utility you never knew…&#34; - Front-End Social</title>
      <link>https://front-end.social/@leaverou/115455940452841916</link>
      <description>// util.js&#xA;export const createSymbols = new Proxy({}, {&#xA;&#x9;get (target, prop) {&#xA;&#x9;&#x9;return Symbol(prop);&#xA;&#x9;},&#xA;});&#xA;&#xA;// Use like:&#xA;const {a, b, c} = createSymbols;&#xA;console.log(a, b, c) &#xA;// Symbol(&#34;a&#34;), Symbol(&#34;b&#34;), Symbol(&#34;c&#34;)&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #utils #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 08 Nov 2025 18:26:39 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37915</guid>
      <category>js</category>
      <category>utils</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Your URL Is Your State</title>
      <link>https://alfy.blog/2025/10/31/your-url-is-your-state.html</link>
      <description>This got me thinking: how often do we, as frontend engineers, overlook the URL as a state management tool? We reach for all sorts of abstractions to manage state such as global stores, contexts, and caches while ignoring one of the web’s most elegant and oldest features: the humble URL.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #urls #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 01 Nov 2025 16:49:44 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37898</guid>
      <category>js</category>
      <category>urls</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Building the Hundred-Year Web Service with htmx - Alexander Petros - YouTube</title>
      <link>https://www.youtube.com/watch?v=lASLZ9TgXyc</link>
      <description>In the fast-moving JS ecosystem, keeping your software current can be a huge drain on resources. But what if there was way to write software that had minimal maintenance burden today and didn&#39;t inspire dread in the junior developers of tomorrow? Built into the web platform are all the capabilities necessary to create useful, networked services that last for decades—we just have to build in ways that takes advantage of them.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #future #js #software #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 17 Sep 2025 18:55:51 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37704</guid>
      <category>dev</category>
      <category>future</category>
      <category>js</category>
      <category>software</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/27b4660a11774c10327265d8b8c45b8c.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>React Won by Default – And It&#39;s Killing Frontend Innovation | Loren Stewart</title>
      <link>https://www.lorenstew.art/blog/react-won-by-default/</link>
      <description>It’s time to choose frameworks based on constraints and merit rather than momentum. Your next project deserves better than React-by-default. The ecosystem deserves the innovation only diversity can provide.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #react #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 16 Sep 2025 16:25:51 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37465</guid>
      <category>js</category>
      <category>react</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Split Flap</title>
      <link>https://fx.hot.page/split-flap?ref=sidebar</link>
      <description>As an ode to the train stations of my childhood, I bring you a skeuomorph split-flap web component&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #js #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Mon, 28 Jul 2025 16:24:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29409</guid>
      <category>css</category>
      <category>js</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/29b4077eb9462985e80dede13833be55.webp" type="image/webp"></enclosure>
    </item>
    <item>
      <title>Plain Vanilla</title>
      <link>https://plainvanillaweb.com/index.html</link>
      <description>An explainer for doing web development using only vanilla techniques. No tools, no frameworks — just HTML, CSS, and JavaScript.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #vanillajs #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 13 May 2025 01:45:32 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29524</guid>
      <category>js</category>
      <category>vanillajs</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Web Performance Calendar » Signals: the nitty-gritty</title>
      <link>https://calendar.perfplanet.com/2022/signals-the-nitty-gritty/</link>
      <description>Mostly revealed to the Web by Solid.js, shortly after embraced by Preact, but also blended into usignal, or implemented by many others, this pattern convinced tons of developers that hooks might not be the best solution to reactivity out there, but while the concept might look and feel super simple and natural to deal with, the complexity behind spans from 30LOC to pretty convoluted code bases.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #js #signals #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 19 Feb 2025 01:40:18 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29654</guid>
      <category>js</category>
      <category>signals</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/7bd9490da5f81c1a07c723718b488fb6.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>1KB Frontend Library - DEV Community</title>
      <link>https://dev.to/fedia/1kb-frontend-library-5ef1?</link>
      <description>Our compact signals implementation is inspired by Andrea Giammarchi’s excellent article on signals. If you’re curious about the nitty-gritty, I highly recommend giving it a read.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #js #signals #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 19 Feb 2025 01:39:53 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29655</guid>
      <category>dev</category>
      <category>js</category>
      <category>signals</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/2519963ae3f203ed09cc97fefbd92b19.webp" type="image/webp"></enclosure>
    </item>
    <item>
      <title>Single HTML Element Star Rating Component - DEV Community</title>
      <link>https://dev.to/alvaromontoro/single-html-element-star-rating-component-205l?</link>
      <description>In this article, we&#39;ll explore how to build a star rating system using a single HTML and just one JavaScript command.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #html #js #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 29 Jan 2025 00:44:29 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29691</guid>
      <category>css</category>
      <category>html</category>
      <category>js</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/5a3f7173dc386c2dd50ebd4d63ee0bb9.webp" type="image/webp"></enclosure>
    </item>
  </channel>
</rss>
