john-doe

There are no “peoples preferences” when it comes to fonts. 99% use the default settings of their browser, so any effort made to improve typesetting of a particular publication is I think more than welcome.

I understand the author’s stance, but it’s probably mostly motivated by the fact that he runs a web publishing service (mataora.blog) where you can potentially write in any script, making it hard to support good multi-script typography without loading webfonts conditionally[0] (also, except for the Noto family, there are almost no universal, good-looking options.)

Thanks to variable fonts, you can nowadays get a full typographic palette (including small-caps, italics, all weights from 100 to 900) on a 300KB budget, sometimes less. The article sports an image that’s 170KB, so it’s a question of priorities I guess.

[0] modern browsers actually got good at this, using unicode ranges: https://developer.mozilla.org/en-US/docs/Web/CSS/%40font-fac...

Javascript doesn’t hurt but becomes another thing to setup and maintain.

You could leave that to Github Pages, if you have basic requirements. (no extra plugins)

Also see: https://10kbclub.com https://0kb.club

English as third language, so let’s say I didn’t realise it was such a strong word.

If the lines are somewhat blurred, you can understand my initial confusion, not being “in the WP ecosystem” myself.

… a 6414-word essay on partnership vs. dominator societies, prehistory, sexism, war-addiction, worshipping nature as a female deity, Çatalhöyük, Old Europe, Hongshan, China, recovery, and the possibility of waking from a ~6,500-year nightmare.

https://twitter.com/tao_lin/status/1461767397711380484

Thanks for the clarification, it's not that easy to understand when one looks at the Automattic website.

> The attack was discovered by researchers at Jetpack, the creators of a security and optimization tool for WordPress sites.

It’s a deceitful way to present it. Jetpack and WordPress are the same company.

https://getpublii.com/ comes to mind too.

Having images was a bit too optimistic I guess, ASCII drawings would have been more appropriate.

… a 6414-word essay on partnership vs. dominator societies, prehistory, sexism, war-addiction, worshipping nature as a female deity, Çatalhöyük, Old Europe, Hongshan, China, recovery, and the possibility of waking from a ~6,500-year nightmare.

https://twitter.com/tao_lin/status/1461767397711380484

> (note to self: clean up and open source my implementation of this)

Please do!

See also: Shiki https://shiki.matsu.io/

@dang plays nice, but OP is being really dense: https://news.ycombinator.com/item?id=29465884

Probably to boost awareness and adoption of new technologies, with the downside of effectively boosting awareness and adoption of new technologies over other considerations, like the web backward compatibility.

The default view of caniuse.com should be “Usage relative”, not “Current aligned”

I wouldn’t say unnecessary; most available comment systems are either a Discuss-style firehose of tracking scripts, or a pain to maintain when self-hosted.

And its clone https://giscus.app/ using Github Discussions instead.

I started collecting examples of what I call “The New Prof. Dr. Style” that shares most of the design constraints/principles of the original, but is mobile-friendly:

- https://urcad.es/

- https://jonathontoon.com/

- https://web.archive.org/web/20210126115413if_/https://maxhaw... (archived)

I think hypothes.is is doing fine.

What were the things your friend was unhappy with, and how did you solve them specifically? Also, I guess someone has to say it, but your bio page weighs a whopping 2.7MB to display a few lines of text, a video embed and a form.

This and the following essays were recently released as an open access book[0] and PDF[1]

[0] https://books.ub.uni-heidelberg.de/arthistoricum/catalog/boo...

[1] https://books.ub.uni-heidelberg.de/arthistoricum/reader/down...

They are. I recommend using `height:0` and `overflow: hidden` instead. Or the more advanced `.sr-only` class: https://kittygiraudel.com/snippets/sr-only-class/

At the time I used padding-top for each of the #elements, the header being absolutely positioned.

More recently I discovered that you can just use `scroll-margin-top: 100vh`, as seen here: https://cadars.github.io/portable-php/

Right… I had it working at some point, I guess :focus-within has some limitations. (This could be solved by :target-within, if browsers implement it someday)