Description
Running Pyret from the CLI misses out on lots of great error infrastructure and the REPL with the most design effort put into it.
Firing up a CPO instance locally takes quite a bit of effort.
It would be nice to support a plain HTML+JS page that hosts the Pyret compiler and REPL. It wouldn't support importing from drive, proxying images, loading non-public tables, or other credential-requiring actions, and it wouldn't save programs except to local storage (or by downloading).
But it would be a nice option for running Pyret from a file:// URL from, say, a plane, where CPO works, but is susceptible to losing the tab due to the browser closing, failing on refresh because something isn't cached, etc.
In the long, long run ServiceWorkers will make this "just work" with CPO. But in the medium-term, something like this would be awfully nice.