This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # alda (2)
- # beginners (52)
- # boot (8)
- # cider (14)
- # cljs-dev (7)
- # cljsrn (5)
- # clojure (4)
- # clojure-belgium (2)
- # clojure-brasil (1)
- # clojure-dev (8)
- # clojure-greece (6)
- # clojure-russia (34)
- # clojure-spec (42)
- # clojurescript (20)
- # cursive (5)
- # funcool (1)
- # hoplon (313)
- # immutant (1)
- # lambdaisland (24)
- # mount (1)
- # om (26)
- # perun (1)
- # planck (2)
- # proton (1)
- # protorepl (6)
- # pure-frame (15)
- # re-frame (14)
- # specter (17)
- # spirituality-ethics (1)
plexus: one interesting track would be to start with the default REPL (`java -jar clojure.jar`), then look at nREPL and why it exists
another interesting track would be looking at the options for cljs REPLs: nashorn, figwheel, plank, node, etc.
interesting, I had been thinking about something very similar, demystifying some of nREPL, piggieback, figwheel
will take some studying, but I've done some spelunking through CIDER and nREPL so that's a starting point
I think I will pretty much have to include episodes on tooling, because right now it's so easy to get lost in those woods
even if you've done some Java before it's a mess, imagine coming from Node or Ruby, you've never heard of jars, or a classpath. Off you go!
this is one of the reason why I have very mixed feelings about boot. Leiningen is far from perfect, but at least it's a standard.
agreed...too often the "formula" for getting started with cljs is "lein new, add these dependencies, then type out these three magic incantations"
the cljs quickstart went a long way toward demystifying the process by revealing that the cljs compiler is just a Clojure program...
I mean, for clj you can mostly ignore that clj code has to be turned into bytecode then loaded in the JVM because it all happens in the same process
but with cljs you have: cljs -> js (one process) -> evaled js (maybe a different process?)
and understanding how the compiled js gets to the js runtime and how that's different between nashorn, browser, node, etc. is interesting
I mean, how many people know that the cljs browser REPL uses websockets? that's cool
personally, it's easier for me to remember the process required and then reconstruct the commands needed than to "just memorize these three commands"
There is already a hidden feature, http://lambdaisland.com/passwordreset . It does not yet allow you to actually reset your password, but it sends you a link with a token that logs you in. Handy if you don't want to type a complex password, e.g. on mobile