100% of the credit for this interactive 3D scene goes to @s3ththompson. It's amazing how adding 3D into the mix totally explodes the space of design possibilities...
Was fun learning this stack for the emissions visualization:
- @idyll_lang as base article framework, with scrollytelling module powered by the scrollama library
- react + react-spring for DOM rendering and animations
- d3 for math and data processing
I gotta say I was surprised by how much work it takes to do a polished scroller visualization 😅
Highly recommend this tutorial which explains how to fit d3 and react together -- it's a lovely combination when done right
I also see @ParametricPress as a fascinating experiment in truly organizing a publication to produce interactive media... We worked with our editor @mathisonian over many months on everything from story concept to debugging babel compilation pipelines 😂
A challenge I'm pondering: this project required a lot of intricate programming, and it feels urgent to enable more people to make interactive media without mucking around in code.
@idyll_lang is on the right track, but so much space to explore...
💫 Excited to share what I worked on this summer with @inkandswitch! We built Cambria, a tool that enables more flexible data compatibility in software.
Here's why I'm personally invested in this research... »
I believe deeply in being able to customize our software tools. But something has been bugging me: if we edit our tools, how does that square with collaboration?
Like, how far can I tweak my writing environment while keeping it working nicely with yours? »
The usual answer is: we all agree to use the same software, or the same file format. But this really limits how far we can tweak.
What if we could fudge around the edges more? Changing the data format while keeping things mostly working together... »
A theory about why tools like Airtable and Notion are so compelling: they provide a much-needed synthesis between the design philosophies of UNIX and Apple.
Short thread:
UNIX is still the best working example of "tools not apps": small sharp tools that the user can flexibly compose to meet their needs.
Once you've written a few bash pipelines, it's hard to be satisfied with disconnected, siloed "apps"
The problem is, while the roots are solid, the terminal as UI is extremely hostile to users, esp beginners. No discoverability, cryptic flags, lots of cruft and chaos.