IntelliJ + LaClojure isn't great.
I'd recommend Emacs + nRepl or Eclipse + CounterClockWise instead.
I realize IntelliJ is better typically but in this case it's not.
I'd recommend Emacs + nRepl or Eclipse + CounterClockWise instead.
I realize IntelliJ is better typically but in this case it's not.
There are clojure plugins for many popular editors these days. If you already have an editor/IDE you like, I'd recommend starting there and moving to something else in the future once you get used to it.
The main reason for this is that so many of the tutorials will assume emacs for your repl management beyond the basic "(car '(foo bar baz))" and any emacs will have a well-defined "manage the indentation and parens"-mode.
Getting help from other people will often involve Emacs-specific instructions as well. "C-c C-e at the end of the sexpr and eval the result..." which may or may not be the binding in Eclipse or whatever IDE the person is using.
> Have you reported them?
Most issues are in your tracker since ages.
> We'd love to know how we can improve it.
merge the lein plug-in into laClojure, or keep it synced all the time.
And implement those requests there in your tracker.
For example, I dislike the yellow warning lines that abound when it can't infer a type that has previously been assigned on all call paths.
This is a desolate wasteland and it's very obvious nobody cares enough to make it work well.
https://github.com/JetBrains/la-clojure/issues
There are issues from TWO years ago with no comments, no explanation, and no fix.
Why would I use your product if I can't trust you to fix anything? With Emacs and nRepl or Slime/Swank I can fix things myself if I need to. Although in practice I don't need to.
If you want people to use IntelliJ, you have to step up to the plate and contribute to stuff outside of the core IDE.
If things like LaClojure are garbage, it makes you look bad and people will start using other tools.
Java programmers that learn Clojure are, (in my experience), leaving their Java IDEs of choice because the support is poor for their new favorite language.
They're coming home to Emacs or experimenting with LightTable.
That makes it your problem. Nobody cares about excuses.
Let me be clear, I don't care if you fail, I'm an Emacs user and believe in programmers maintaining their tools for themselves out of deep mistrust for commercial entities owning how programmers do their work. But if you want to be competitive you have to stop being myopic.
Have you been paying attention? Companies like http://zeroturnaround.com/ make their product free for Scala users because those people are the vanguard for their respective communities and will often be the ones making product decisions.
There is a comparable thing going on with YourKit's wonderful support of the Clojure community.
How exactly are you staying on top of the latest developments in JVM languages if you're concerned exclusively with "IntelliJ-the-IDE-itself"?
My point about it being on our GitHub account and OSS is that the source is available, much like it is for plug-ins for Emacs or Sublime or any other environment. It's not about blaming anyone or pushing the effort on to someone else.
We have quite a few developers dedicated to writing plug-ins in-house, specially considering pretty much all the functionality in IDEA is based around plug-ins and in fact we have around 3 people that are working alone on Scala plugin.
> ... and in fact we have around 3 people that are
> working alone on Scala plugin.
It is not only that I can't see much progress with IntelliJ's Scala plugin and that the free Scala IDE is getting increasingly better as well as having some amazing add-on functionality.
I'm really wondering how much money of their Scala customers JetBrains is really spending on improving the Scala plugin and how much of it is silently funnelled into FUD and vaporware factories like Kotlin.
That's a huge conflict of interest and the reason why a significant part of my next paycheck probably won't end up in JetBrains bank account.