4 ms·
It depends on the language you're using (working with Scala is usually slow). Also, make sure that IntelliJ caches are on an SSD. VS is very quick, but for exam
by sz4kerto 12y ago
It depends on the language you're using (working with Scala is usually slow). Also, make sure that IntelliJ caches are on an SSD. VS is very quick, but for example parsing C# is very easy compared to Scala (partly because C# was designed for that from day zero). Maven also slows down things a bit (IntelliJ can search in classes that are not even referenced by the project.)
- nothrabannosir 12y agoGood points. I have no SSD, unfortunately. There are two types of slow: there is slow to react, and slow to respond. I can understand that IntelliJ is having a hard time recompiling the Scala source. As you said, Scala is difficult to parse and compile. What I don't like is the context menu taking several seconds to even appear, locking up the entire UI (!), when I right click. Or music playback going haywire just because I am switching files or refactoring. Setting it to "low priority" solves that last issue, but that doesn't make me feel better about IntelliJ. If an app is slow, fine. But deal with it. React quickly, respond later. PS: I say that now, but once I have a better computer, it's all "IntelliJ is great." I only feel this way because my computer can't take it.
- tormeh 12y agoI've heard that the correct way to parse a Scala program is dependent on the types in it. I think maybe that's why IDEs are so wrong about where your errors are unless you terminate each statement with ";"
- brianwawok 12y agoNever used a ; in scala and my IJ is pretty dang good at figuring it out. Catches maybe 95% of errors, and SBT will catch the last 5%. (Okay sometimes you can use a ; in a for comprehension to be fancy but you don't usually need to)
- amyjess 12y agoI gave up on IntelliJ and went back to NetBeans because of the bass-ackwards way IntelliJ handles Maven projects. There's no need for both IntelliJ's project file and the POM to track dependencies. In fact, there's no need for IntelliJ to maintain its own project file at all outside the POM.
- sz4kerto 12y agoWell, you might need both. The POM only contains information on how to build the project, while the IntelliJ project file also contains extra information that might be personalized, things like tab size, JDK version, and millions of other things. My policy is to only put the POM into VCS, and keep the .idea stuff only on the local box.
- amyjess 12y agoNetBeans just has the nbactions.xml file, which defines a small number of things like the main class and some context menu actions (this is very useful for OSGi projects, where you often have to switch between different build/run profiles). It's pretty lightweight, and it leaves everything else to the POM. Oh, and on that note, that wasn't the only reason I left IntelliJ. I also disliked how it handled having multiple projects open. If you don't want everything in separate windows, IntelliJ makes you create a dummy project and import everything as modules. NetBeans just does what I want automatically.
- brianwawok 12y agoWhere does the POM specify the path to the JDK you should use to compile with? Where does the POM specify the project specific code formatting you want to use? Where does the POM specify the exact JVM flags and params given to various launch configs?
- rpcope1 12y agoFYI if someone is reluctant to give up their HDD capacity at the price point an SSD exists, I've had really good luck with IDEA and Pycharm on my Seagate 2.5 1 TB Hybrid (ST1000LM014). I think they can be found on NewEgg for like $70 (for 1 TB), and work well for the sort of caching IDEA tends to do.