3 ms·
> To use it effectively, however, requires using an IDE, and Flubbists hate IDEs, partly because their finger muscle memory has been overspecialized from spend
by baldfat 11y ago
> To use it effectively, however, requires using an IDE, and Flubbists hate IDEs, partly because their finger muscle memory has been overspecialized from spending too much time in Eighties power editors, but also because using an IDE is too closely associated with Blub practices. (People who can't ride a bicycle without training wheels, basically.)
This also has an attitude. Certain things an IDE is almost required, for example Data Science with a REPL. IDEs like RStudio and Jupyter (AKA IPYthon) or for SML dialect Racket's REPL.
Also this is anti VIM and EMACs?
- stevedonovan 11y agoEver so slightly ;) I think it admirable that people invest a lot of time in the environments they spend so much time in, but a professional has to be flexible. (It is entirely possible that my sarcasm got out of control here.)
- veddox 11y agoJust out of curiosity, what makes you say IDEs are bad?
- baldfat 11y agoThe article is negative about IDEs. I was stating that in fact IDE can be a valuable tool for specific areas.
- marcosdumay 11y agoIDEs aren't bad, but... Automatic code generation is bad (unless its completely automatic in "you don't ever see it"), because code always have to change, and changes aren't automatic. Heavyweight building setup is bad, because you can not replicate or automate it. Long names everywhere hinder legibility. (Although long names on confusing or ambiguous places are a good thing.) And, finally, people learning to program should learn how to program without one at some point, so they know what they are doing. None of that makes IDEs bad. It just neuter their biggest selling points, but there are lots of small gains you can get from one.