It's nice to see people getting passionate about this sort of thing, but it's incredibly alpha, and atm it doesn't seem to have any features worth writing home about. At least, not from what I could tell after playing around with it for a little bit.
I'm the creator of Nightcode, and I agree, which is why I didn't announce it here. It is pretty half-baked and I was hoping to fix some of the more obvious bugs before promoting it more. That being said, I can't really complain.
I see this (very cool-looking) IDE has one-click Clojure Android project skeletons. I'm in the midst of Android development, and find that Java is slowing me down more than I would have anticipated. I just can't sketch out ideas like I do in scripting languages. So my question is: how is Clojure on Android these days? I know that historically, it's had some performance issues. Are these getting better? Is interaction with the Android API pretty seamless?
I'm half-tempted to use Nightcode just to spare me the pain of trying to set up a Android project using Clojure. If any of the previous non-Java languages I've used on Android are any indication (Python and Lua, mainly), it's a huge pain in the ass. I really wish Google had built a more polyglot-friendly environment in Android.
This is amazing..
The greatest thing you have done ( I havent checked out the whole IDE yet ) is to reduce the whole step of setting things up down to 1 click.. The biggest gripe I had with Clojure / Cljs was the setup process.. I am not familiar with the java world and I hate setting things up before getting my hands dirty. This sir, does everything for me.
Although I agree that LightTable is a more polished clojure IDE, it doesn't do the one thing that ganarajpr mentioned: create lein projects for you through the UI.
Even though lein is easy to use, integration like this lowers the barrier to entry for new folks wanting to learn clojure, which is awesome.
Doesn't anyone else find it odd that command-line tools would be a barrier to entry for programmers? Sure, I see it all the time; I just don't get what people are expecting.
I just released 0.0.2, so those who are having issues with running and building on 0.0.1 may have better luck this time. It also now correctly uses command instead of control for keyboard shortcuts on OS X.
As I said before, it is still a very early release, so please let me know about other bugs you find.
I'm using IntelliJ which has so far been great for great for Clojure and Java plus every other language I use. I'm definitely willing to give this a shot and I also want to know if you're looking at doing any Scala support?
I'm in the same boat - I've been a very happy IDEA user for over a decade now, and any other IDE that targets the JVM has a pretty high bar as far as I'm concerned.
With that said, I'd love to see the Scala equivalent of this - the Scala plugin for IDEA works fairly well (they still have quite a few problems with inline error highlights/parsing when your Scala code uses path dependent types), but the Typesafe official Scala IDE uses Eclipse, which utterly rules it out as far as I'm concerned.
A lightweight but functional Scala-native IDE with builtin sbt support would be absolutely awesome for a pure-Scala project.
I write Clojure and Scala, Clojure got me into Emacs and then Emacs+Ensime led me away from IDEA for Scala development. I recommend it fully.
I am a big fan of IDEA and use that for Java and Groovy, and also Jetbrains' AppCode for Obj-C development, but the Scala support in IDEA is currently just not good enough.
I can't really give you a fair comparison, I've only used Xcode enough to know that I don't like it.
I don't even think the full switch can ever be made. Because it's Apple development, everything is in an "Xcode project" (instead of, say, "iOS project"). So even using AppCode I'm still dropping back to Xcode some of the time.
> A lightweight but functional Scala-native IDE with builtin sbt support would be absolutely awesome for a pure-Scala project.
This would indeed be wonderful. I have been using Scala as my first language of choice for some time now and personally feel that Scala is still held back a bit in terms of tooling. Please consider this!
Would this be a good resource for learning Clojure for someone who's a rather inexperienced programmer? I remember looking at Leiningen a while back and being a little lost. I've heard really good things about Clojure and functional programming in general but I still have my programmer training wheels on.
After reading through that, the exercises at http://4clojure.com/ helped me to solidify things and learn what the core library has available. Work through a problem on your own and then check out how someone like 'immo' or 'jbear' did it.
Yeah I definitely made Nightcode with newbies in mind. Like I said before, it is half-baked and probably too buggy for normal use right now, but eventually I hope it serves as a good entryway for Clojure and Java programming.
I've been planning to learn a modern (compared to Interlisp, which I used in the 80s) Lisp for a long time. What stops me is the need to 1st learn a very complicated IDE.
I'm also having some doubts about Clojure compared to true Lisps - those store all data as lists for a very good reason - it allows fantastic code reuse.
About your last point, Clojure's seqs enable code reuse. You can operate on lists, vectors, sets, maps, etc as seqs. I don't know about Interlisp, but Common Lisp does not unify these datatypes under such a common sequence abstraction.
Yes, I had Rhodes' work in mind. In Common Lisp, sequences are hardcoded as lists and vectors. [1] Which excludes the sets and hashtables (which I mentioned), not to mention anything sequence-like which users might come up with. (Actually, it doesn't even have sets built in. I've seen people use degenerate hashtables to simulate them — keys which just hash to true.)
Furthermore, the by far most common mapping functions operate only on proper lists, not sequences. [2] And in the very popular (albeit notorious) LOOP macro, one must even use in/across/"k being the hash-key using (hash-value v)", depending on whether you're operating on lists, vectors or hashtables respectively! [3]
(Of course, one could add these things to CL, in the sense that you have all of CL's power in C — by implementing CL atop C. Or you could invent your own generic seq functions, and hope others use it.)
Someone could point out that had CL's standard had continued to evolve, it might've had these things. Or that these limitations were due to weaker computers. But whatever happened happened, and this is the real-world CL we have. CL's a wonderfully powerful language (not counting the troll-dominated community), but there's seams.
I am unlikely to witch my Java IDE away from Netbeans and unfortunately Netbeans does not have any support for Clojure. (Enclojure is dead).I wish someone would would develop a Clojure plugin for NB. That would solve a real problem for those gently switching to Clojure.
I like the idea and might contribute to the source.
I have the feeling the response to keystrokes is somewhat delayed? Type "asdf" for example and you will set it takes perhaps 1.5x more than it should and its not even.
there are quite a few editors to code in clojure and I don't see how you can differentiate from the others, but good luck, it looks promising. I personally use macvim/vim.
Emacs + nrepl if properly set up is really the killer combo. You get instant popup-style access to documentation, auto-complete, repl and unit test integration.
with paredit the ( ) handle themselves pretty much.
I'm having success introducing even my noob programmer friends to Clojure by directing them to install Leiningen (Clojure's build tool) and Lighttable (editor with integrated repl).
Generate the project skeleton:
$ lein new foobar
Open up folder `foobar` with Lighttable, and you can begin evaluating code in your source files (it starts you with foobar/src/core.clj).
It's nice to see people getting passionate about this sort of thing, but it's incredibly alpha, and atm it doesn't seem to have any features worth writing home about. At least, not from what I could tell after playing around with it for a little bit.