Chris Shank has been on sabbatical since January, so he’s had a lot of time to think deeply about the web platform. On this episode, Jerod & KBall pick Chris’ brain to answer questions like, what does a post-component paradigm look like? What would it look like if the browser had primitives for building spatial canvases? How can we make it easier to make “folk interfaces” on the web?
:link: https://jsparty.fm/338
I'm only halfway through and have had a little glance through Chris's example repos. The approach reminds me of the Elm architecture, which centred IIRC around a single massive sum type with all the possible actions the user could take in the app, like Flux architecture action names. I never got to use that model in anger, it just seemed... both so sensible and so awkward to have one type for your whole app.
RE "you have an HTML file but now how do you share it?" An underrated capability is that you can just send an HTML file in an email or messaging app, same as you would with an image! Of course browsers don't like you doing this, and block APIs if you're opening a local file. I also doubt mobile browsers will open local HTML files :(. But HTML files are a great place to start!
Mobile browsers don’t like them, but on iOS you can open them via Shortcuts like so. 9B1A665B-B858-403E-8A8F-1AB9AA5C4CEA.png
Last updated: Dec 12 2024 at 16:47 UTC