It seems as if every single key press, whether or not it affects the output (for example, writing in a comment or hitting enter to reorganize and space out code) causes every single function to be evaluated again.

You can test this out by adding something like this...

(time (+ 1 1))

...and start typing in a comment on a new line and seeing how the elapsed time that is outputted changes on every single key press. Performance optimizations are probably not as important right now, but that's something that can be improved.

Still, as a basic test of the concept, it looks pretty interesting overall and I can see myself using this. As long as the idea is sound, everything else can be improved over time. Keep it up!

For Linux the script is doing "if chrome, else if firefox". Better to use xdg-open.

So it's looking for Chrome, a closed source browser that I'd never use, instead of Chromium. Too bad.

Seems like you can use any browser you'd like by going to: http://localhost:8833/

once the server is up and running.

Thank you, that's cool! How can I kill the server, though?

  light server stop

if you look through the script file, it has a series of options.

  light table
  light server start | stop | restart
  light update [version]

but as far as I can tell it always checks for updates first and will install them before it checks any of the arguments passed.

>So it's looking for Chrome, a closed source browser that I'd never use, instead of Chromium. Too bad.

TMI.

You are of course free to use or not use anything you like, but the above sounds entitled and self-centered. At this point, who the duck cares if YOU are "never gonna use a closed source browser"?

It's a post about a new editor in a pre-pre-alpha stage. Something like "Seems to be requiring Chrome. Why such a restriction?" would be far better, no entitlement, no open/closed source zealotry, not tied to specific personal preferences regarding source license, etc.