“Decoupling HTML, CSS, and JavaScript in design systems - Go Make Things”

Been doing a bit of research in various JS/web dev online communities and, wow, there’s a lot of bad advice out there. Stuff like “you should never use the form element in a modern framework” 😰

“You should be ready, willing, and able to read the source code of your dependencies -> Changelog”

This is great advice. And getting into the habit of reading other people’s code will improve your own.

“Let’s Talk about Native HTML Tabs - daverupert.com”

Interesting proposal. Could work.

“Willingness to look stupid”

This is really good advice.

“CSS { In Real Life } - Evaluating Clever CSS Solutions”

I’m not the only one worried about the popularity of ‘clever’ solutions in the CSS community.

I wrote a short blog post on reading for skills development: you need to change how you read and apply new reading strategies if you don’t want to plateau.

www.baldurbjarnason.com/2021/what…

“How I Structure My CSS (for Now) · Matthias Ott – User Experience Designer”

Is ITCSS the most influential CSS strategy that nobody really talks about? See it’s influence almost everywhere these days.

“Fix web accessibility systematically · Eric Eggert”

“Learning to build conviction - benkuhn.net”

I guess winter has arrived.

The view from my kitchen window. A snow-covered, parking lot, buildings, trees, and landscape.

“Blaming Screen Readers 🚩×5 - Adrian Roselli”

“Joyce and Walky! » The baby can hear stuff now”

“Software developers have stopped caring about reliability”

This x1000. There’s been a shift in software dev away from reliability and usability. All of the incentives line up against them.

Remember this Chrome headless bug that I’ve been obsessing about?

Turns out that this is a known bug in Chrome headless on Linux. To fix it either turn off hinting or subpixel positioning

github.com/puppeteer…

Screenshot from Chrome headless where the text rendering is all over the place Another screenshot of unreadable text

“Some reasons to work on productivity and velocity”

“Custom properties with defaults: 3+1 strategies – Lea Verou”

I don’t mind the verbose solution, personally, but these are all good tactics.

“Implementing form filling and accessibility in the Firefox PDF viewer – Attack & Defense”

PDF.js is an amazing library. I just wish it were better documented.

“The dark side of Eureka: Artificially induced Aha moments make facts feel true - ScienceDirect”

“Was it easier to build websites a decade ago? - Go Make Things”

Absolutely agree with this. The modern web is capable of amazing things. You don’t have to do it the hard way. (I mean, yeah you do if your boss is dead set on it, but you know what I mean)

“Every search bar looks like a URL bar to users – Terence Eden’s Blog”

So, it looks like the kerning/spacing problems I saw in the PDF output of puppeteer/headless chrome on Linux wasn’t just an issue with a single font. Snaps from a test file: Literata, EB Garamond, and Inter

A screenshot of a sample text showing very ugly spacing issues. Literata, which is a readable serif font.A screenshot of a sample text showing very ugly spacing issues. EBGaramond, which is a pretty but less readable serif font.A screenshot of a sample text showing very ugly spacing issues. Inter, which is a very nice sans-serif font.

“CSS is Going Gosh-Darned Hog Wild, I Tell Ya What - CSS-Tricks”

CSS is easily my favourite part of the web stack.

“Appwalls and their apps are destructive to the open web. - Airbag Industries”

So, it turns out that the typographic quality of Chrome’s PDF output varies quite a bit OS to OS.

Subjective assessment:

  • macOS: really good
  • Windows: not bad, though not as good as macOS
  • Desktop Linux: same to marginally worse than Windows
  • Headless Linux: quite bad.