3 ms·
This blog post isn't insightful and doesn't even manage to present a consistent case against IDEs, and boils down to a sequence of weak strawmen. Describing a I
by rewmie 3y ago
This blog post isn't insightful and doesn't even manage to present a consistent case against IDEs, and boils down to a sequence of weak strawmen. Describing a IDE's job as making it easier to type is pure nonsense and fails to even acknowledge what a IDE is and what it adds beyond text editors. In the very least, IDEs make it easy to navigate projects and run searches for things like source files or symbols, with the latter supporting types of searches not available in pure text searches such as finding where a function of a particular subclass is called.
This sort of article fall into a fallacy trap which is failing to understand what "integrated" in "IDE" means, and proceeds to fail to address what exactly is integrated.
- kmoser 3y agoYou can extrapolate the whole "IDEs are a crutch" idea to pretty much any tool that saves time by automating something you would have had to do manually. High level languages hide the underlying machine code being generated, so developers become less familiar with what the CPU is really doing. But in a way that's the whole point. In the end, newbies will rely on the crutch to develop faster at the expense of not immediately understanding all that is happening behind the scenes, while more experienced developers will leverage the IDE to automate those things which they are tired of doing themselves. Eventually newbies learn what's happening under the hood.
- delta_p_delta_x 3y ago> You can extrapolate the whole "IDEs are a crutch" idea to pretty much any tool that saves time by automating something you would have had to do manually. You're not a real developer if you don't write in binary /s