Re:0xDBE: JetBrains IDE for DBAs and SQL developers
by mahmoudimus on Monday June 09, 2014 @01:54PM
(#7869545)
I'm a big fan of IntelliJ, I'm not sure I agree w/ this - though it might be specific to your use case.
Can you note some specific features that are missing? I understand if one application requires a different way of doing something, but that doesn't necessary mean that functionality is missing or different.
Re:0xDBE: JetBrains IDE for DBAs and SQL developers
by btipling on Monday June 09, 2014 @03:06PM
(#7869897)
One big set of features missing are the configuration options available in PyCharm. For example being able to configure Vagrant in PyCharm provides its own UI in the IDE settings. I have created a screenshot showing all the various PyCharm setting views compared to IntelliJ with the Python Plugin installed:
You can actually get some of the Vagrant features with a separate Vagrant plugin in IntelliJ, but PyCharm lets you set up the Python interpreter with Vagrant via a really nice UI.
Re:0xDBE: JetBrains IDE for DBAs and SQL developers
by mahmoudimus on Monday June 09, 2014 @03:58PM
(#7870157)
Of course, that makes sense. That feature is under the Remote Interpreter in IntelliJ. Vagrant configurations can change between modules, which is why it's organized under IntelliJ under module settings -> SDKs.
So that falls under "hidden under a different area" in the IntelliJ project, not missing functionality.
The concept of modules in IntelliJ is not in PyCharm, I believe. Though, I could be wrong.
We actually buy a license for each of these editors. We test our Floobits plugin for IntelliJ in each of these editors and they are significantly different enough that you should really have a copy of each. They also have different build numbers and different jar libraries included. This means there are differences in the code base and that could affect a plugin you might be building.
For example PyCharm ships with apache java libraries we also ship, and we used to have conflicts when PyCharm had a really old version. The different build numbers indicate different points of history in the IntelliJ code base. Some crucial plugin API may be in one build but not another.
Thankfully Jetbrains gave us a steep discount for the licenses to help us out. But even if I were not editing a plugin for Floobits I would still have to buy a license for PyCharm, WebStorm and IntelliJ separately because the Python and JavaScript plugins for IntelliJ do not have all the features the separate IDEs have.
I took a long time to setup Django and virtualenvs correctly so I can run and debug Floobits.com in PyCharm, I don't see any easy way to translate that work from PyCharm to IntelliJ with the Python plugin. Same with WebStorm. Many of our services are written in node.js and translating my setup from WebStorm to the IntelliJ plugin with JavaScript doesn't seem easy to do or even possible. It might just be I have no idea what I'm doing.