The best CSS Framework? I don’t know. Complexity moves in mysterious ways. The many interpretations soc model must be satisfied.

1. CSS in CSS (canonical)
2. CSS in HTML (write once and time driven)
3. CSS in JavaScript (framework driven)
4. CSS in Shadow DOM (company/department driven)
5. CSS in Scoped Formats (IDE driven)
6. CSS in Preprocessors (design system driven)

I’d say, choices reflect environmental factors (social or otherwise) at play. If you’re lucky enough to choose, then suitability favors what draws the finish line closer? I’ve no advice since I’d rarely have the time/luxury to choose anyway. I’m usually thinking about the possibility of more types, sub–types (i.e in #1: bem, classless, etc), and the transposition strategy and speed between each class/type.

Text fragments are a Chromium feature from a couple years ago. They (#:~:text=) emulate CTRL + F or window.find() from a URL. I experimented in times past with a snippet–like approach using <mark> with URL encoded terms on id + :target logic, such that clicking this link highlights the paragraph below.

https://web.dev/text-fragments/#:~:text=Text%20Fragments%20let%20you

After perusing the web dev blog feeds (finally).. it seems that there’s a “mainstream” coordination away from the client side;

• https://intercoolerjs.org/
• https://unpoly.com/
• https://htmx.org/
• https://turbo.hotwired.dev/handbook/introduction

Time until a transition to ‘json over the wire’? These are very handy libraries btw — I tried htmx previously.

So as you may know we have, knowledge.. or in the old black books of web witchcraft; the checkbox hack. I wonder though; did anyone ever go the final mile and create a kinda generalized “progressive polyfill” to fix the semantics of this so called hack?

Tangentially, a query for a details/summary polyfill brings up either rstacruz/details-polyfill or chemerisuk/better-details-polyfill with demo. Interesting.

A no build repository for SolidJS. Don’t ask. I found this splendid repository while strategically traversing the void. Demo.

I used up all my free time points last month experimenting with a Guile Scheme webserver. Then I discovered ZelphirKaltstahl/guile-examples… Haunt is also an interesting static site generator.

When making hugo themes, it’s probably better defaulting to absURL and relURL over baseURL for links. It avoids most breakage on links that depend on a base and more easily allows multilingual support with absLangURL.

However realistically (for anything), interpretations of file, directory/, absoluteness, and relativity are varied. Testing artifacts for ≈ 100% internal/self linking consistency, under different conditions, and after every code change is better time spent debugging. Sub directories are exceptional cases.. even now some of my links are broken except that my web server automatically fixes common mistakes (:

The Chrome experimental recorder tool has been around for a long while. I thought it was still mostly wip but I got schooled and apparently, this is a more faster way to jump–start a puppeteer script/test:

Which browser engine “paints” HTML the smartest on my device? In the clip below; Surf substitutes for Safari and Chromium for Chrome. My blog is the testee since there’s guaranteed cache control and jitter.

Surf and by extension Safari (or any Webkit–based browser) wins imo. Webkit feels smooth (sneakily, too smooth). It’s probably partly why Safari on macOS/iOS feels so fast. Chrome (not Chromium) is almost on par or so I’ve been told. Not exactly web dev but interesting huh?

Profiling is the nice, cozy, and lazy way to efficiency. There’s something neat about avoiding optimization and having the numbers to prove it relative to an initial baseline. In PHP there’s Xdebug and KCachegrind and I recently saw php-spx in my feeds. A profiler in any language environment with snapshots of performance over time is just — well nice. The terribad situation is not understanding exactly how something became slow. It might be too late then.