This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-11
Channels
- # announcements (16)
- # aws (4)
- # babashka (30)
- # beginners (58)
- # bristol-clojurians (4)
- # cider (9)
- # clj-kondo (2)
- # clojure (229)
- # clojure-europe (25)
- # clojure-gamedev (1)
- # clojure-italy (4)
- # clojure-nl (13)
- # clojure-sanfrancisco (1)
- # clojure-uk (97)
- # clojured (7)
- # clojurescript (27)
- # code-reviews (2)
- # cursive (30)
- # data-science (39)
- # datomic (14)
- # emacs (12)
- # events (2)
- # fulcro (6)
- # graalvm (8)
- # graphql (14)
- # jackdaw (10)
- # jobs (2)
- # lambdaisland (5)
- # malli (4)
- # off-topic (28)
- # protorepl (13)
- # quil (7)
- # re-frame (2)
- # reagent (1)
- # reitit (3)
- # remote-jobs (5)
- # ring-swagger (1)
- # shadow-cljs (72)
- # sql (4)
- # tools-deps (182)
- # uncomplicate (4)
- # vim (9)
- # xtdb (19)
heya, is anyone using protorepl?
I think most ProtoREPL users migrated to Chlorine once ProtoREPL stopped being maintained (and, I think, was broken by changes to Ink?)
(no updates to ProtoREPL in almost two years now 😞 )
Ah, thanks for the response. I just found it and the features look amazing, but yeah ran into several breaking issues
There's a #chlorine channel and the maintainer is super responsive.
thanks for the tip, I'll check it out!
I'm curious why so many promising editors seem to not work out
I posted some videos on YouTube showing how I use Atom/Chlorine with Cognitect's REBL. Plus I also have https://github.com/seancorfield/atom-chlorine-setup which has some additional setup for Chlorine (esp. if you use REBL).
ProtoREPL was great for several years. I switched from Emacs/CIDER to Atom/ProtoREPL after I saw Jason show it off at Conj one year.
I liked Atom enough to stick with it, so I was happy when Chlorine appeared (esp. since I wanted to get away from nREPL).
What don't you like about nREPL?
I'll answer that by saying what I prefer about Socket REPL: it's built into Clojure -- no dependencies; any Clojure process can start a Socket REPL with zero code -- you just add a JVM option when you start the process; that means you can REPL into any process, regardless of whether you planned ahead; all those REPLs are the same -- so your dev tooling can work exactly the same way with your local REPL and your remote processes.
I also really like "spartan" tooling -- like Stu Halloway talks about (in conference talks and on podcasts) and Eric Normand also seems to support in his REPL-Driven Development course on http://PurelyFunctional.tv 🙂