Nice data, it is clear that the IDE argument is not so false after all, and I totally agree that editors like VIM and Vs Code are way better than IDE's like eclipse, NetBeans or that crap that jetbrains offers.
It is sad too to see how Sublime Text is slowly dying... It is getting to much behind from the others, even that of Atom. And we all know its performance sucks.
On the other hand if Microsoft moves away from Electron, Vs Code will be unbeatable, much like chrome is on the browser market share space.
I guess it really depends on what you work on. I do .NET development and couldn't see myself not using Visual Studio - I consider it the best development tool I've ever used. That said, I've had terrible experiences with Eclipse and Netbeans when doing Java development though I don't know how much was the editor or the language so its not an IDE vs Non-IDE thing.
When I've done PHP development though, I am using VS Code. I tried Atom but found it crashing too often. Prior to that, I actually used Geany which is probably an uncommon editor for Windows.
I saw very heavy Visual Studio use in a .NET shop, but when I was doing .Net core development, I exclusively used VS code. It is more light weight and integrates with C# nicely. It is possible, given the right stack, to do C# without VS proper.
I keep VS around for this very reason. If I'm working on a C# or .NET project it's tooling is very well tailored to that work, including additional niceties like break statements, inspections, and memory and CPU profiling.
For Node, Ruby, and Python I almost exclusively use VS Code.
I've been a developer/software engineer/software architect for over 25 years, and you'll only take my JetBrain's IDEs out of my cold, grey, dead hands.
I can always tell the code people write in VIM, Sublime, Notepad, VSCode, etc. because the code is filled with bugs that my JetBrain's IDEs flag for me and make sure they are errors I do not make.
I don't see the difference.. Linters and the language server protocol are available for all editors too, I personally think that if someone writes bug filled code on a specific tool, it is not the tool for the blame, but the programmer.
Sure it is the programmer's fault. It's their fault for not choosing good tools! He or she would have less reason to be blamed had they used better tools.
By the same logic, mechanics don't need wrenches, they only need hammers, and they should treat everything like a nail and bang on it. That makes no sense.
Good IDEs can make good developers better because they help them learn the language better than they would if they were left to scratching their head trying to understand why something does not work in a text editor. In an IDE the developer can read the hints that explain why it does not work and learn from them. I have been learning Go for the past 3 months and GoLand has been a godsend!
A good engineer knows that one of the most important aspects of being a good engineer is to pick the best tools for the job (and yes, I am a degreed engineer.)
That said, if you think working in a text editor is best for you, more power to you.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice data, it is clear that the IDE argument is not so false after all, and I totally agree that editors like VIM and Vs Code are way better than IDE's like eclipse, NetBeans or that crap that jetbrains offers.
It is sad too to see how Sublime Text is slowly dying... It is getting to much behind from the others, even that of Atom. And we all know its performance sucks.
On the other hand if Microsoft moves away from Electron, Vs Code will be unbeatable, much like chrome is on the browser market share space.
I guess it really depends on what you work on. I do .NET development and couldn't see myself not using Visual Studio - I consider it the best development tool I've ever used. That said, I've had terrible experiences with Eclipse and Netbeans when doing Java development though I don't know how much was the editor or the language so its not an IDE vs Non-IDE thing.
When I've done PHP development though, I am using VS Code. I tried Atom but found it crashing too often. Prior to that, I actually used Geany which is probably an uncommon editor for Windows.
I saw very heavy Visual Studio use in a .NET shop, but when I was doing .Net core development, I exclusively used VS code. It is more light weight and integrates with C# nicely. It is possible, given the right stack, to do C# without VS proper.
I keep VS around for this very reason. If I'm working on a C# or .NET project it's tooling is very well tailored to that work, including additional niceties like break statements, inspections, and memory and CPU profiling.
For Node, Ruby, and Python I almost exclusively use VS Code.
I've been a developer/software engineer/software architect for over 25 years, and you'll only take my JetBrain's IDEs out of my cold, grey, dead hands.
I can always tell the code people write in VIM, Sublime, Notepad, VSCode, etc. because the code is filled with bugs that my JetBrain's IDEs flag for me and make sure they are errors I do not make.
I don't see the difference.. Linters and the language server protocol are available for all editors too, I personally think that if someone writes bug filled code on a specific tool, it is not the tool for the blame, but the programmer.
Sure it is the programmer's fault. It's their fault for not choosing good tools! He or she would have less reason to be blamed had they used better tools.
By the same logic, mechanics don't need wrenches, they only need hammers, and they should treat everything like a nail and bang on it. That makes no sense.
Good IDEs can make good developers better because they help them learn the language better than they would if they were left to scratching their head trying to understand why something does not work in a text editor. In an IDE the developer can read the hints that explain why it does not work and learn from them. I have been learning Go for the past 3 months and GoLand has been a godsend!
A good engineer knows that one of the most important aspects of being a good engineer is to pick the best tools for the job (and yes, I am a degreed engineer.)
That said, if you think working in a text editor is best for you, more power to you.