3 ms·
This feels like a crock statement. A Sr developer who's efficient uses every tool at their disposal to be efficient and productive. Primitive IDEs and text edit
by adra 4y ago
This feels like a crock statement. A Sr developer who's efficient uses every tool at their disposal to be efficient and productive. Primitive IDEs and text editors may help your geek cred score, but as a long term java dev who's moved into Kotlin and go recently, vs code was borderline terrible and very limited in what I wanted in features. I never used intellij until my most recent company (eclipse mostly beforehand) but they really do a good job at streamlining the dev flow. I do miss eclipses much more dynamic layouts and arguably better integration with some external technologies, but idea's Kotlin integration has been top notch and makes for quite brisk in-the-flow coding experience like no other.
As for hitching and speed, intellij has a poor 15 seconds on my laptop before it's super snappy and basically never drops perf whatever I'm hammering at. I think the common feature rich IDE slowness strawman is a defence for what's better expressed as an opinion. If you like featureless ides, have at it.
- deleted 4y ago[deleted]
- sangnoir 4y ago> This feels like a crock statement. A Sr developer who's efficient uses every tool at their disposal to be efficient and productive. Correct: and in my case, VS Code with my customizations (plugins + configs) is more than equal to the task, it does everything I'd want from a full-blown IDE, and does it in a snap. Being disrupted by your IDE is maddening because it only happens when you're in deep focus. My IDE journey was similar to yours Eclipse -> Jetbrains, then what started off as a casual affair with VS Code on personal projects ended up being serious indeed. I felt like it was easier to add features I want to VS Code than to remove/disable fearures from IntelliJ to trim the fat, YMMV. I'm glad to hear IntelliJ s now consistently fast after initialization - when I last used it, the slow downs were unpredictable and lasted minutes, and occasionally required restarting the IDE, but that was a long time ago, back when SSD storage was expensive.