nyc-based programmer. @recursecenter alum.
public transit enjoyer. thoughts on local-first, javascript frameworks, web components, css and other web minutiae.
| www | https://jakelazaroff.com |
| til | https://til.jakelazaroff.com |
couldn't make it to #atmosphereconf so i've been cooking at home instead
i'm pretty excited about this one: a way to build real-time collaborative apps with *no dedicated sync infrastructure* โ just some static files and atproto
https://jakelazaroff.com/words/building-more-resilient-local-first-software-with-atproto/
building a typeahead web component has convinced me that we need to standardize reference target, like, yesterday
https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md
part of me is scared to let go of my precious state-based rendering but part of me wants to dust off jquery and party like it's 2006
RE: https://mastodon.social/@jakelazaroff/115321887318884153
put another way: i don't want your data. I *never* want your data. and not just from an ideological "users should be in control" perspective, but also from a pragmatic "this makes my app more difficult and expensive to run" perspective.
we've been so focused on making it easy to scale *up* that we accidentally made it hard to scale *down*
this really resonates with me. i like making little personal web apps for myself and my family and friends. the most annoying parts โ the parts that drastically increase the scope, from "a bunch of HTML, CSS & JS files i can serve from anywhere" to "a web server and database i need to continually maintain" โ are auth and persistence. so i am *very* excited about atproto including a user-owned solution for both.
