(p.s. is "we turn out (...) agree" a riff on the Finnegan's Wake epigraph?)

A suspicious preponderance of em-dashes, though.

We're planning to provide some mechanisms so that it should be possible to build a roam-inspired plugin/framework on Rheo with a small amount of Typst, yes!

The code is open source: github.com/freecomputin...

If you use Typst or want a static site generator that supports references and footnotes natively and elegantly, give it a try! I'd appreciate any feedback if you do, as it's in early development (not production ready).

Seems a chaotic design decision, I agree. @tonofcrates.bsky.social has a great post about how generally chaotic the e-reading ecosystem is: willcrichton.net/notes/portab...

I personally feel that gastown is most impressive when you think of it as an art project simulating capitalism. Materality disavowed, executive direction at the expense of any attention to the particularity of resources, ethical legitimacy established through a rhetorics of yoohoo-- a fine nutshell.

Mainly it feels cooler. Git gives hard-grooves and bad blood over Linux kernel dev, jj is like fresh snowfall on a mountain.

And we studied Shakespeare AND John Donne, so this is saying something

"what does this vaingloriousness down here" is one of the most useful retorts I learned in my high school English class: www.poetryfoundation.org/poems/47266/...

surely beta blockers work as a form of doping in cricket, especially for opening batsmen? I say this knowing next to nothing about the history of doping in the sport.

Version control, and code review. The ability to notice when something's not being done well is now as key to coding 'alone' as it has always been to coding collaboratively

I really appreciate this synthesis! I'd love to hear more about how you see the branding exercises of 60s/70s CS being resuscitated in 'data science' and AI departments in the 2020s-- if you see any parallels, the (quite different, I think) economic logics pulling strings behind the scenes, etc.

Writing code has never been the bottleneck of good engineering; REASONING about code is the real labor

And I recommend her lucid and remarkably honest post about her own job seeking process to all who are currently on (or dabbling in) the market, too:

This is such an excellent book and anyone who is serious about programming should read it!

Or: it is the discipline (category theory, philosophy) that presumes explain everything, whereas the rest of the domain (science, the humanities) has the general sense it explains next to nothing.