Colin Yates <colin.ya...@gmail.com> writes: AFAIK LightTable has paredit or sth. similar. Also, a great deal of customisation is available via ClojureScript. I am personally favouring Emacs as I am a polyglot programmer and do not only use Emacs as an editor, but the programming and computing environment: This post is sent via Emacs (Gnus), I write my blog posts with it, run shells, use git (magit) and even view photos and PDFs.
If all you look is an editor/IDE-ish though, Emacs and LightTable are quite the same thing indeed, except for the fact that Emacs has better community and more packages. > Without starting a flame war - how are you finding LightTable for > production? Moving away from emacs and paredit would be quite hard and > every time I look at LightTable I get really excited until I actually > download and try it... That is almost certainly because I don't have the > time to invest in learning it and I expect it to do everything out of ethe > box immediately and just the way I like it :) > > On Tuesday, 4 February 2014 17:13:04 UTC, Sean Corfield wrote: >> >> Discussions around TDD / RDD (REPL-Driven-Development) probably need a >> separate thread but... >> >> On Feb 4, 2014, at 5:17 AM, Mimmo Cosenza <mimmo....@gmail.com<javascript:>> >> wrote: >> > thanks for the report. I only have few doubts about REPL making TDD to >> shame. >> >> I'm a strong advocate of TDD (well, BDD specifically) and I agree with >> Jay's comment insofar as you write a "test" expression in the REPL and it >> evaluates immediately. That's always faster than writing a test and running >> a test, by definition. That's all I took his comment to mean. >> >> > The REPL is great, that's for sure, but IMHO it does not relegate TDD >> feedback/loop in a niche, because you can complement one with the other. >> >> Indeed you can - and Jay does - and so do I. Especially now I'm using >> LightTable and can evaluate code in place in amongst my production code in >> one tabset and my expectations in another tabset. I have C-c , bound to >> evaluate a "run-tests" expression in my namespace so I can quickly evaluate >> and execute tests. Even so, live evaluation of "test code" is still a >> faster feedback loop. >> >> Many of my test expressions become long-lived unit tests (expectations). >> Or they become production code. I still write expectations to clarify how >> to design APIs in the small (and APIs in the large as needed), but most of >> the red-green-refactor loop of TDD/BDD now comes from the REPL experiments >> for me. >> >> Sean Corfield -- (904) 302-SEAN >> An Architect's View -- http://corfield.org/ >> >> "Perfection is the enemy of the good." >> -- Gustave Flaubert, French realist novelist (1821-1880) >> >> >> >> -- — gk -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
