engineer, writer, "artist"
Two updates:
(1) I'm leaving the tech industry. Hopefully "for good"; at the very least, "for now"
(2) If you subscribe to my blog, the content's gonna change; I'm dropping the editorial focus I've had since 2020 and going back to writing about whatever the heck I want. Some of the same stuff, some new stuff, we'll see.
More here: https://jacobian.org/2025/jun/3/changing-directions/
@omad jujutsu's a good one, very recent and gamechanging for the people who use it (not me yet but soon)
@dareelcatskull pedantically, i was thinking about writing a redux of this article from 2022 https://macwright.com/2022/11/18/optimism-updates - and thinking of good stuff from the ~2023-2025 period proved tricky so i decided to throw it into the fediverse. M chips are a big deal and strongly agree on that point
besides ai, what's the biggest good new change in the last 3 years in the tech world for you?
@cassidoo fun challenge! my semi-golfed solution for nestArray: const nestArray = ([i, ...r]) => (r.length ? [i, nestArray(r)] : [i]);
@TimmSL i use the obsidian-geocoding-properties to add geospatial frontmatter to existing notes https://obsidian.md/plugins?id=geocoding-properties - and in the here plugin, there's an option to choose a POI from google places and add it as a new note with pre-filled frontmatter
for the #obsidian folks… i've wanted the ability to see 'nearby notes' and create new POI-based notes based on my current location, and just got a working prototype together called obsidian-here. test it out if you're similarly minded! https://github.com/tmcw/obsidian-here
@dareelcatskull thanks! designed it a decade ago and i change a few lines of css a year to make it more itself
the story's all kind of in the title of this rant https://macwright.com/2025/05/29/putting-an-untrusted-chat-layer-is-a-disaster
@spzb @mvexel at this point i'm just as jaded about modern web frameworks as i am about the backlash. a lot of the react critiques are like this take on government waste https://www.youtube.com/watch?v=Zoz5EuIF_y8
@ingenieur yep, archivebox already uses puppeteer internally but there are some core chromium bugs that lead to memory leaks, plus running a browser, even under puppeteer is just very resource-intensive
@ingenieur getting outgoing links is super simple, the archivebox part is taking that big list of extracted links and archiving all those webpages, and that part is hard - it's running headless chrome, eating up ram, doing it slowly, etc
been trying to archive all outlinks from macwright.com with #archivebox and results are decidedly mixed: tasks keep getting stuck in a 'pending' state with no feedback as to whether anything is working or not.
@marcpfister no, these are amazing! maybe for version 2
i wrote that post (this took a bit of work!) https://mastodon.social/@tmcw/114529687520866775
Sewing together a custom porteur bag: https://macwright.com/2025/05/18/sewing
@kellan just up to brewster this time, but two years ago now (?) i did hudson back to brooklyn, which was also great (although a little hillier and a little more on streets once you get farther north)
@wooorm haha, yeah, i haven't dug into </div/>… technically everything is parseable as html5 afaik but the <div/> syntax is interpreted the same as <div> which leads to this unusual behavior https://stackblitz.com/edit/stackblitz-starters-5acumdx6?file=index.html