As the other commenter points out, the ui-react (and in turn ui-react-dom) modules are optional so you can run it with full ReactDom, with abstract React (eg React Native), or without React at all.
The way to do that would be to listen to data changes (eg addCellListener) and in the listener just manipulate the DOM directly. Probably a pretty slick approach, performance-wise.
For SQLite, a variety of flavors are supported including things like ElectricSQL, Turso, and PowerSync - which all let you sync back to a server. You might also consider running a ‘client’ on a server that can listen to changes coming through web sockets and persist itself to server storage - but I haven’t written that pattern up yet.
Hopefully you’ll get a chance to try it out in the meantime though!
Fantastic travel writing with a couple of real LOLs. The author plays the role of self-aware snob for all it's worth though, I assume hoping that his fellow passengers and Atlantic readers are disjoint sets.
It’s a proof of concept! But hopefully you can see how you could build an app that has content that is both cloud & local, private & shared - and that has users that are both anonymous & authenticated, online & offline.
Thanks! Yep, I think we need an about page, and maybe a few pull quotes from the articles. The first article from Ink & Switch is the canonical source of the name and the idea.
I think a lot of web consumer products (and dare I say SaaS too) are these days _not_ on your own computer like they were in the 90's or early 2000s. This isn't a call to return to those days, but it is a reminder that there have been trade offs in moving our productive lives entirely to other people's computers - both in terms of technical performance, but also conceptual ownership and the like. Can we rebalance a little?
So yes, the idea is exactly _not_ new. But a lot of products are built today without considering this tried-and-tested architecture as an option. This site & list of tools is just a friendly reminder that yes, there is another way.
Author here. I’ll try and fix this. I have a suspicion it’s the CSS glow behind the logo since everything else is the most stupid basic HTML you could imagine.