(no title)
oreganoz | 7 years ago
Because I've been interesting to get an excuse and try Clojure out and what you're saying is really interesting.
oreganoz | 7 years ago
Because I've been interesting to get an excuse and try Clojure out and what you're saying is really interesting.
hellofunk|7 years ago
Clojurescript offered the first and still (in my opinion) best option for hot reloading via "figwheel" which nearly all Clojurescript developers use. It automatically updates the UI as you code it.
Clojure, on the server, being a proper lisp with a real REPL, lets you poke and inspect and reload parts of the running program with no recompile cycle. A typical workflow there is to reload individual expressions or functions in the context of the running program to alter behavior as you develop.
oreganoz|7 years ago
Can the REPL on the server be used to update production systems with no downtime?
asragab|7 years ago
https://github.com/bhauman/lein-figwheel
has that out of the box. As for an actor model implementation, there is pulsar:
http://docs.paralleluniverse.co/pulsar/
Which has erlang-like actors, though some might suggest that core.async and its channel implementation provides everything you might need an actor for, YMMV.
oreganoz|7 years ago
My main interest with actors is that these can be made to support hot code reloading on the server side. They also tend to be easily composable. Also also, they can be optimized by locality (eg. same-node, same-cluster, different-cluster)
I'm biased though, having not worked with CSP or other models.