I've been using a hand-built oklch CSS colour system for a few personal projects recently, and decided to open source it!
Announcing openswatch v0.1.0.
I’m convinced one aspect of RTO is re-enabling managers’ abuse of (some) lost power. When I worked in an office I had managers try and stop me going home, or follow me part way home because “work really needs to get done”. Much harder to pull shit like this on a zoom call.
Just open sourced i-html, a modestly sized web component which allows dynamically importing of html fragments inline. It enables some surprisingly nice patterns.
A few years ago I was all in on k8s. Had myself a home lab so I could learn what I was sure would be required knowledge by this point. Gitops with flux, helm, istio etc. I realised it’s the same set of complexity demons that live in the front end. So I dropped it and went “back” to docker but I still couldn’t shake that feeling. The complexity demon still lurked. So most recently I’ve been scp-ing binaries and writing systemctl scripts and oh boy does it fuckin rock. I’m never going back.
I feel like CSS nesting somewhat makes “css modules” redundant. CSS modules try to scope everything to one selector but a lint rule enforcing a single top-level rule per file would enable that, meaning the only other benefit is name collision avoidance which could be solved with another small piece of tooling or sensible directory design.
