JsCoq
github.com
github.com
A real REPL (i.e. in your shell, not in your browser) that uses MathJax or whatever for result rendering would look much more interesting to me.
If the universe ever comes to an end it will be because it has been rewritten in JS.
Insert joke about theories that the universe is a simulation here.
I will add, I think it can be very disheartening for people who put a lot of their own time into making something happen and then having a random commenter say, 'Yeah, but I would rather have had something else, that wasn't at all the project you set out to make.'
It's only "brutal" if you're compiling from source, in which case you've got to compile all of the ML and then all of the Coq libraries. That's only necessary for experimental branches though; I've not used an OS which doesn't provide binaries of official releases.
The installation process is basically "apt-get install coq && coqide", or whatever package manager your system uses. That will run the GTK interface which comes bundled with Coq.
The only time when Emacs might have anything to do with Coq is in relation to Proof General; but the only reason to run PG is if you're already an Emacs user. It's been in maintenance mode for years, and being rapidly overtaken by asynchronous interfaces based on PIDE (eg. the jEdit and Eclipse plugins).
I'm a very happy Emacs user, but just because I use Coq via PG doesn't mean I'd ask non-Emacs-users to do the same; in the same way that I access my GMail account via Gnus, but wouldn't try to convince non-Emacs GMail users to do the same.
I hear what you're saying, but that's the risk you must take when you do a public display like that. Besides, it's at least half the fun. What's the use of only fanboys (& -girls) commenting, if that's not the whole picture?
You don't have permission to access /rhino-coq/ on this server.
At least the devs have a sense of humor.
https://en.wikipedia.org/wiki/Functional_programming#History
http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay...
So functional programming isn't a reaction to OOP.
It's also the case that Python is not particularly OOP (it does seem to me that lots of people that came to it from Java use it that way).