Visual Studio is basically a mini OS. You can subscribe to news feeds and web surf inside of it. You run setup, you wait until it finishes and bam you are ready to start coding. There are definitely benefits to that philosophy, especially for new developers.
On the other hand, I've recently switched to a job where I spend all of my time in Unix terminals and I can't image ever going back.
That's one way of putting it, yeah. And the same criticisms that were applied to emacs (so bloated, uses lots of RAM, etc) apply equally to Visual Studio (or pretty much any other IDE out there).
Curious. I spend much of my time nose deep in visual studio. It seems like an awesomely efficient ide. What is it about working in terminals that is superior?
For me it's more than just dev environment. I spend even my childhood in Linux (from age 9). I dont know how to use windows anymore. If people need help with their computers (use windows) I dont know what to say until I see their desktop so I can figure out how it works :P
So I am so used to programming and working with linux and terminals that I can work faster on that than using Visual Studio or something.
Needless to say, I do run some sexy IDE's on the side like WebStorm and IntelliJ IDEA and Atom (all for different purposes)
Think of UNIX and its commandline tools as one huge IDE. All the tools are available always, there's no difference between "in the IDE" and "in the filesystem". It's really jarring for me to use IDEs now, they are so... walled-garden, compartmenalized and brittle.
That said, as long as you do exactly what the IDE wants you to do they are fine (or even better at that task), I guess. It's the same as with any walled garden.
I've used both, and I wouldn't really say there is that much of a difference in productivity. They are two very different styles of working, but either can make you as productive. Both have its "weak points" that slow you down, although they are very different.
In the end though, the bottleneck to actual productivity when programming is not really the environment, once you are "settled in".
Is 2 gigs of RAM really a big deal these days? 16gb for a desktop seems reasonably standard, so we are potentially saying it takes up 1/8th of the memory.
This is the problem with Microsoft, they've got all those fancy DLLs, yet NOTHING is actually encapsulated into it's own section, so they just keep reinventing the same shit.
39
u/keef_hernandez Dec 06 '15
Visual Studio is basically a mini OS. You can subscribe to news feeds and web surf inside of it. You run setup, you wait until it finishes and bam you are ready to start coding. There are definitely benefits to that philosophy, especially for new developers.
On the other hand, I've recently switched to a job where I spend all of my time in Unix terminals and I can't image ever going back.