3 ms·

What are the issues you've found with IntelliJ? Have you reported them? We'd love to know how we can improve it. Please feel free to ping me (hadi at jetbrains)

by hhariri 13y ago

hansg 13y ago
> What are the issues you've found with IntelliJ? > 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.
- reeses 13y ago
  The gradle/groovy integration is of only slightly better harmony. It's very obviously a plugin and the lack of analysis makes for an awkward dynamic programming experience. 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.
rickjames28 13y ago
Does LaClojure have a blog or some kind of "news" page where we can find out what the latest developments have been? All I've found is the github page.
- hhariri 13y ago
  Currently, apart from the GitHub pages, there isn't anything.
coolsunglasses 13y ago
I'd like an actual Lisper to work on LaClojure. Also, I'd like anybody to work on LaClojure. 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 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.
- hhariri 13y ago
  But the plugin is OSS and on GitHub. Or are the issues in relation to the IDE itself? (which btw the community edition is also OSS and on GitHub)
  - coolsunglasses 13y ago
    Nobody cares about which part you're responsible for, they care about how nice the tools are. Saying it's OSS and not your problem is weak and looks bad. Especially given it's on your GitHub organization! 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/ 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"?
    - hhariri 13y ago
      Who says we're paying attention only to the IDE itself? Apart from the fact that we support a wide variety of languages on the platform, both JVM targeted languages as those that are not, and that the fact that we're also developing our own OSS language, kind of is contrary to us only focusing exclusively on the IDE or the tools. 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.

What are the issues you've found with IntelliJ? Have you reported them? We'd love to know how we can improve it. Please feel free to ping me (hadi at jetbrains)

by hhariri 13y ago

What are the issues you've found with IntelliJ? Have you reported them? We'd love to know how we can improve it. Please feel free to ping me (hadi at jetbrains)

hansg 13y ago

> What are the issues you've found with IntelliJ? > 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.

reeses 13y ago
The gradle/groovy integration is of only slightly better harmony. It's very obviously a plugin and the lack of analysis makes for an awkward dynamic programming experience. 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.

rickjames28 13y ago

Does LaClojure have a blog or some kind of "news" page where we can find out what the latest developments have been? All I've found is the github page.

hhariri 13y ago
Currently, apart from the GitHub pages, there isn't anything.

coolsunglasses 13y ago

I'd like an actual Lisper to work on LaClojure. Also, I'd like anybody to work on LaClojure. 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 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.

hhariri 13y ago
But the plugin is OSS and on GitHub. Or are the issues in relation to the IDE itself? (which btw the community edition is also OSS and on GitHub)
- coolsunglasses 13y ago
  Nobody cares about which part you're responsible for, they care about how nice the tools are. Saying it's OSS and not your problem is weak and looks bad. Especially given it's on your GitHub organization! 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/ 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"?
  - hhariri 13y ago
    Who says we're paying attention only to the IDE itself? Apart from the fact that we support a wide variety of languages on the platform, both JVM targeted languages as those that are not, and that the fact that we're also developing our own OSS language, kind of is contrary to us only focusing exclusively on the IDE or the tools. 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.