re: The Rise of Microsoft Visual Studio Code VIEW POST

TOP OF THREAD FULL DISCUSSION
re: 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 ha...
 

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.

code of conduct - report abuse