3 ms·
> Shun IDEs Well, I don't think anybody is "shunning" IDEs just to be difficult; it's just really, really hard to describe something in the context of an IDE.
by commandlinefan 9y ago
> Shun IDEs
Well, I don't think anybody is "shunning" IDEs just to be difficult; it's just really, really hard to describe something in the context of an IDE. For one thing, IDEs are (obviously) graphical, so you have to include a screenshot if you want to refer to something. Worse, IDEs change things around a lot (sometimes for no particular reason). Then of course, there are no standards in this area - in Java you have Eclipse and IntelliJ, so if you want to describe something in terms of an IDE you either pick both and double the explanations, or you pick one and freeze out the others... or you just do everything on the command-line which is unambiguous. And don't forget, eventually you're going to have to get out of the IDE comfort zone if you want to interface with a continuous integration system.
- dan_mctree 9y agoCommandline instructions fail as often as IDE based instructions do. Changes in different versions, changes in the environment, different ways of trying to use the software, different ways projects were set up; all of these and many other reasons cause plenty of issues with commandline based instructions. It's never "just do everything on the command-line", it's "it just spewed out an essay of errors on step 2, and google is silent"
- TimJYoung 9y agoIt's not really that hard, though. Almost everything you see in an IDE is just a pretty version of something in a text file somewhere. IDE's don't get rid of project files, source files, object files, etc. They just simply manage the complexity in a way that keeps what you need at your fingertips.