| <waves> I've personally gone back and forth over the years between IDEs and decent editors for programming in C, C++, and Java. I started programming before there were IDEs, so perhaps that has some influence, but you did say "...stopped using IDEs once they started". I like some functionality of IDEs, but most are barely "nice to have", not "must have" -- the thing I find that I miss the most is language aware navigation. The thing that keeps bringing me back to just using a reasonably powerful editor (for me, that means either Vim or VSCode, both with zero or very, very few extensions) is the lag between new features coming to existing languages (and new languages emerging) and IDEs supporting them in a non-disruptive manner (never mind fully). With a decent editor, web or manpage based docs, and a command line based build (which I want anyway for releases and/or CI), I'm all good, thanks. I mean, if I were to be working someplace that required or depended upon an IDE, I'm not necessarily averse to using one again, but that might be a red flag for me regarding that workplace. I certainly get the appeal of IDEs, and understand that some find more value in a powerful IDE than in using the latest language features. Both ways of working are reasonable, depending upon your situation, goals and preferences -- I wish more folks would understand that. |