3 ms·
The only thing an IDE brings to the table is a different user experience. A better user experience can be beneficial, but is not akin to giving up tooling. Ther
by randomdata 3y ago
The only thing an IDE brings to the table is a different user experience. A better user experience can be beneficial, but is not akin to giving up tooling. There is no reason (purposeful attempts at vendor lock-in aside) for the same tools to not be available outside of the IDE.
It's more like GUI vs the command line. Both can ultimately get the same job done, but the experience is different. And, frankly, I'm not sure there is one winner takes all. Sometimes GUIs allow you to do more, better, and be more efficient, but other times it is the command line excels at those things. There is situational dependence.
- janosdebugs 3y agoNot quite so. You need to explicitly run a linter, then look up the code lines that it's complaining about. In an IDE, you will have the lines marked while you are writing the code. Plus you get code completion and so on. Working in a pure text editor works if you have a relatively small piece of code you can focus on while working, but I've seen very experienced engineers become extremely slow or completely fail with their vim setup when they suddenly work on something that's beyond the 20k line mark.