Earlier quoted context omitted.
I often use WebStorm (Intellij variant), and I am continually annoyed by its inability to keep up with my typing. I do like the IDE, but I do wish it was more responsive. It often feels like a heavyweight, taking long to do any operation, especially starting up.
I've never seen anything that tried to do intellisense in JavaScript that wasn't slower than molasses. The quickest way for me to get Visual Studio to crash is to open two or three small .js files, watch the memory usage skyrocket, and the editor speed grind to a halt.
Kotlin Is Better
221–229 of 229 posts
Re: Kotlin Is Better
#222Earlier quoted context omitted.
> Without type annotations, refactorings are never safe There is a difference between "I can prove this is safe" and "this is safe". You guys need to start figuring out the difference between theory and practice.
In practice, "this is safe" often transforms to "I thought this was safe" at the most inopportune moment.
Re: Kotlin Is Better
#223A few people have said that IntelliJ is slow. Why is this so, if Java is not inherently slow? Sure JetBrains are some of the smartest developers around and yet their IDE is still slow. I can't help but feel that Java is slow and problems with performance in something like IntelliJ do nothing to dispel that feeling.
IntelliJ is written in Swing, which 10 years ago was certainly slower than an alternative UI framework like SWT. Not sure if there is a noticeable difference nowadays.
Re: Kotlin Is Better
#224Earlier quoted context omitted.
I also encountered way more IDE bugs in Scala than in Java. Actually during the full last year of development of a real-world commercial Scala project I encountered 0 bugs in Java and 2 bugs in Scala. What about more objective measures? Scala plugin issue tracker: 11667 issues. Kotlin plugin issue tracker: 17664 issues. And this difference is despite Scala being longer on the market and being more popular than Kotlin…
How on earth is this an objective measure for plugin quality? There's so much you can interpret into these numbers that they are borderline meaningless.
Re: Kotlin Is Better
#225Earlier quoted context omitted.
> We tend to use tests for just this case. You change anything you want, then see which tests break, and fix all the places. Why not tests + static typing? Getting tests to point out breakages is attempting to do job the compiler can do for you but not as well. If you renamed a field in some places but not others for example, you'd have to rely on good enough code coverage to catch this plus deciphering a failing tes…
> rely on good enough code coverage to catch this Wait, you don't enforce 100% coverage? (Sorry, couldn't resist ;)) I actually mostly agree, static typing is a huge boon for productivity, and certainly allows for less experienced (both new programmers, and new to the project) developers to become productive on a new codebase faster. However, I think dynamic typing forces a certain familiarity with the codebase that…
Re: Kotlin Is Better
#226The "ew gross weird" reaction to Scala and Clojure is tremendously disappointing (especially coming from someone whose thesis is basically "give this new language a chance")
Clojure startup times are brutal, and simply not workable in the mobile environment where Android lives.
Re: Kotlin Is Better
#227A few people have said that IntelliJ is slow. Why is this so, if Java is not inherently slow? Sure JetBrains are some of the smartest developers around and yet their IDE is still slow. I can't help but feel that Java is slow and problems with performance in something like IntelliJ do nothing to dispel that feeling.
Because IntelliJ does a lot of work. Similarly, Visual Studio is not usually slow but sometimes it will mysteriously become so slow as to become unusable, or at least that was true a few years ago when I spent a lot of time in it.
Re: Kotlin Is Better
#228Re: Kotlin Is Better
#229Anyone knows how it performs versus, say, Clojure for server-side development ?