It astounds me that there is no text editor on iOS which gets everything right (like syntax highlighting) for writing about programming, and in fact none which do everything right on modern iOS, including keyboard and now pointer support, Files support, and syntax highlighting.

Lightroom CC needs an update to work with the new iPad Magic Keyboard and trackpad. Once it has that, it’ll be down to one or two features to be hands-down better than the desktop version. (Which is pretty astounding, if you think about it!)

With today’s This Week I Learned and issue of Across the Sundering Seas, I’m somewhere north of 50,000 words published this year. Now, if only some of those were essays…

Status: I’m back to desperately wanting my own site engine. 11ty is incredibly flexible, and that’s great… but it gets slow very quickly if you’re generating large amounts of output. I will not shave this yak. I will not shave this yak. I will not…

Next thing I’m thinking about with rewrite (while trying not to over-think): design systems! I want to build this in a scalable, maintainable way.

Last night I threw away almost all the build config I’d been blinded by this spring while working on rewrite: webpack config, TypeScript integration, you name it. What I have left: a simple bunch of npm scripts that I can run in parallel in different terminal sessions:

{
  "scripts": {
    "clean": "rm -rf dist/*",
    "build:static": "cp static/* dist",
    "build:css": "sass --load-path=./node_modules src/style.scss dist/style.css",
    "watch:css": "sass --watch --load-path=./node_modules src/style.scss dist/style.css",
    "build:elm": "elm make src/Main.elm --output dist/app.js",
    "watch:elm": "watchexec -w src 'elm make src/Main.elm --output dist/app.js'"
  }
}

It’s not fancy, but it gets the job done just fine for the things I’m actually working on — rather than things I’ll need eventually — and that’s exacty the right balance at this point.

TypeScript: it’s regularly absurd or weird, and I am frustrated regularly by so many things about the type system… but nearly all of them come down in practice to “this works this way because JavaScript and JavaScript developers.”

A thing that has gotten way better since the last time I was messing with MIDI stuff: almost all hardware supports USB out now, instead of needing insane MIDI-to-USB adapters.

Having used the iPad Magic Keyboard for a couple weeks now, and having typed on the one on the 16″ at a store a few months ago, I’m officially ready for this to be an external keyboard for my desktop Macs, too. It feels really good.

Dear readers (and listeners-to-music!): I thought I had nothing to share from today’s composing… but I was wrong! I made some progress! If you saw the Day 5 post when it went up, pop back over and give the update a look’n’listen.

Status: just emailed my old composition professor at OU asking for recommendations on orchestration books. ♬ The one class I really wish I’d taken while studying composition.

A pain point for would-be readers with the way I’ve designed this site: there’s no easy way for people to subscribe to just one specific topic at present. I can generate per-topic feeds… but I’m already seeing painfully-rapid growth in build times.

Well, it only took me till almost six months after launching this site revision, but the About page is finally finished!

I got curious, and (after some command-line shenanigans) figured out that I’ve written/collected about 22,000 words of notes in my Zettelkasten so far in 2020. That’s… a lot of notes. 😅

Things fancy cameras cannot help with: setting your 𝑓-stop too low so you don’t get everyone in focus.

New approach to goals: write a little every morning, work on rewrite a couple evenings a week. Trying to make massive amounts of progress is hard right now for a variety of reasons, but if I can make a little progress every week I’ll get somewhere.

Apologies to folks who just got a bunch of posts in their feeds again. I finally figured out how to get Eleventy to treat my post dates correctly.

Weird but true: I really, really love writing docs. It’s always one of the most satisfying parts of any project for me.

Between my new This Week I Learned entries, an interest in having all my notes in one place, and a desire to actually use my notes system more effectively I’m trying something new with my reading: notable things I read (and my comments on them) will now live in Bear instead of Pinboard. I expect this will help a lot with active review of my reading notes. (I may go ahead and do something I’ve thought about for a while and pull all of my Pinboard notes over to Bear, too!)

I just updated the first entry in my “This Week I Learned” series because I realized I’d left off a couple items I meant to include — the first items I bracketed for inclusion, in fact! What can I say? It was a long week. 😅

Almost nothing makes me as irritable as tendentious or hagiographical histories. Don’t glamorize or villainize the people of the past: tell the truth.

With today’s issue, I have officially made it through a quarter year of publishing Across the Sundering Seas on my target schedule. A nice little victory!

Trying out cursor support on iPad OS 13.4 for the first time this evening, as well as having remapped Caps Lock to Ctrl (as it should be), and… the experience is simultaneously incredibly delightful and really, really weird. Weird in a good way, but weird.

Perhaps the single most-broken thing in iOS’ Files app: the fact that you cannot specify a default app to open a file in. An arbitrary app wins. It’s infuriating.

Status: working on figuring out how to wire up Elm and Rust-via-WebAssembly using webpack. I’ve spent the last four years in Ember and before that I was wiring up Gulp. So this is new. 😅

Quick Git tip: if you’ve manually edited your Git configuration file and removed a given remote, you may find yourself in a spot where you now have a bunch of branches associated with that remote… which you cannot delete. The only way (I could find) out of this problem was to re-add the remote, and then run git remote rm <the name of the remote>. That deleted the remote and all the references to its branches

Wanted: something like The Archive, but for iOS. Bear is beautiful and I love it, but I want my notes on disk because then I can do anything with them from anywhere — not just what one app can come up from. (And yes, a document object model like people dreamt of in the 90s would also solve this well, but for today I’ll take what I can get.)

And yes, this is what I’m working on with rewrite.

I’m not quite sure how this had never occurred to me before the last week or so, but I ordered some refills for my current favorite gel pen and it only at that point occurred to me that I could put those refills in a different pen case. 😂 At some point I’ll have to try that.

One of the critical things Jira gets wrong — besides just generally having pretty bad information architecture — is that it treats issues as a tree instead of a graph. But that’s often not how projects and tasks actually relate to each other!

After digging in further: Zig is not doing quite what Rust is. It is an updated C, which eliminates some of the worst foot-guns, but fundamentally does not try to eliminate memory-unsafety… which profoundly disappoints me, even if I still wish Zig success.

Zig is the first language that I’ve seen which seems interested in seriously playing in the same space as Rust.

And it does it in a substantially different way, which I like! It feels (reading docs) kind of like a “doing the kinds of things Rust does but with C instead of C++ as its direct competitor.”

I really, really wish GitHub had a slightly lower entry point for Teams/Organizations. I’d like to do everything for rewrite in a single organization on GitHub, rather than all under … but $25/month is frankly kind of steep for one developer. I’d be happy paying $10/month for just organization management, with the jump to $25 for supporting multiple developers. As is, though… GitLab looks appealing, whatever its other weaknesses.

This feels good. Substantial increase of January’s time and mileage… despite the fact that this ended up being something like the 4th snowiest February on record along the Colorado Front Range! I spent a loooooot of time running in the snow this month.

A quick sketch of an idea which I hope to test out by the end of the day: the best way to handle “responsive” routing in an Elm app — for a master-detail view where the master view isn’t visible when at a detail route on screens below a sufficient size — is to just use a port and send a message on screen size change.

Parenting is without a doubt both the most rewarding and the most tiring thing I do, full stop, bar none. My daughters are amazing, and also they are full-fledged humans with all their own wants and needs… but still very little practice as yet at being humans.

I’ve spent a good chunk of this afternoon working through and tweaking and fixing some things about this website, and as much as I like 11ty, at this point I would love to be doing this work in Elm instead. A tool like elm-pages seems very appealing.

As for why: I just spend a lot of time sad about JS “sorry bro that’s undefined” stuff and templates being totally type-unaware. Even something like Gatsby + TS would probably be better here, but Elm’s rigor and top-to-bottom integration of types and rendered HTML and CSS would be a huge win for the way I build websites.

I just got curious so I looked up: Winning Slowly has published 120 episodes in the last 6 years! Sloooow but steady (as is only right 😂). Averages out to ~20/year, which is surprisingly high given the last couple years, but we were churning them out fast those first couple seasons.

This is, perhaps, a little odd, but: one of the little things I’m most excited about with Winning Slowly right now is that — at long last, and years overdue — we’re actually doing something with Patreon. We’ve had it, and had minor benefits for it for a long time. Now we’re taking it seriously: keeping it up to date, publishing extra materials there, etc. Crazy talk, I know!

One thing that makes me eager to upgrade to the next-gen iPad when it comes out (…and I’m actually seriously contemplating the 12.9″ this time around) is how fabulous it is to be able to do the entire workflow for things like cameras on it with just normal cables.

It is already my default device for photo editing (Lightroom on iPad is 💯) and I think it’s going to be my default for podcast editing after having done Winning Slowly 8.03 in Ferrite. (To anyone interested in podcasting, I’d absolutely recommend Ferrite over anything else out there at this point. The experience of editing a podcast with that app and an Apple Pencil is just phenomenal.)