4 ms·
All good points, but chiming in that I'm actually going the opposite direction on VSCode. I've used VS Professional for 70% of my dev up until recently, but mo
by shireboy 6y ago
All good points, but chiming in that I'm actually going the opposite direction on VSCode. I've used VS Professional for 70% of my dev up until recently, but more and more and finding I can do the same things "lighter" with VSCode+appropriate extensions.
- nolok 6y agoAgreed and when I open intellij, it's clear mentally that I'm "working", while ss code makes me mentally feel like "I'm just doing a quick edit", even after 5 hours of coding. It's juste the perfect amount of lightweight but with just all the features I need to be productive. But at the end of the day there are always those 10+ people projects, or hard debugging case, where a heavy computing-intensive IDE figguring stuff out for you is worth every cent. Anyway my general point is make sure your tool suits you, if you spend more than 5 minutes fighting against it every day it doesn't, you either need training on it or to change it.