3 ms·

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)

by hhariri 13y ago

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.
  - dubbledodimm 13y ago
    > ... and in fact we have around 3 people that are > working alone on Scala plugin. As a paying customer who bought IntelliJ solely for its Scala plugin, I'm currently seriously questioning whether it is still worth paying for the next version. 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.
- hhariri 13y ago
  Also, IntelliJ Community Edition is OSS and free. Available on GitHub as well as downloadable from our site. So not sure what you would need in terms of making the product free. We also have quite a few community programs where we provide licenses, and OSS projects can qualify for free licenses to ANY of our products.

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)

by 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.
- dubbledodimm 13y ago
  > ... and in fact we have around 3 people that are > working alone on Scala plugin. As a paying customer who bought IntelliJ solely for its Scala plugin, I'm currently seriously questioning whether it is still worth paying for the next version. 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.
hhariri 13y ago
Also, IntelliJ Community Edition is OSS and free. Available on GitHub as well as downloadable from our site. So not sure what you would need in terms of making the product free. We also have quite a few community programs where we provide licenses, and OSS projects can qualify for free licenses to ANY of our products.