The Arcology Garden

A Modern User Agent


You can not trust the internet to design your user-agents. content companies and surveillance capitalists cannot be trusted to build user-agents, and doing so has been and will continue to be a mistake.

up in to the early 2000s even it was possible to use a fully native and local set of applications to communicate, research, learn, and entertain. this has been steadily eroded away as expectations rise

before this it was DOS and a more "give it a little more elbow grease" times that I lack experience of

what does "emacs for the web" look like? a trustworthy user-agent which exposes its internal state for users to extend and build upon, to nimbly fit to their needs. fundamentally a communication tool as much as it is a productivity tool.

emacs in pre-web era was the user-agent if you so chose in a way that is impossible today. due to proprietary APIs hidden behind React SPAs and mobile apps. an emacs for the web is necessarily revolutionary, it seems like?

does it have to be written in a lisp-like? "why can't i write emacs plugins in javascript?" <<lisp purist answers go here>>

is "emacs for the web" a web application or is it a web browser? can it be both?

the logical answer here is "use clojure and clojurescript" but the toolchain isn't terribly accessible, in a way that i do'nt know how to explain right now. resource-constraint is tough, clojure feels expensive. java adjacent ecosystem feels suffocating?

i've been happy with elixir, though, in some toy examples that I've been working on. phoenix liveview is pretty incredible. phoenix is pretty incredible.

and so i'm building a web application. it'll be a PWA and i'll do the work to make push notifications work. an emacs for the web built around the ideas in

for now.