Benefits of Not Using an IDE

Post by 988747 » Sat, Aug 21, 2021, 5:51 PM UTC

dharmab wrote: post #164

jcelerier wrote: post #109

Earlier quoted context omitted.

> - Error highlighting. this so much. it's priceless to just type a line and have some warnings such as "hey, you're moving this value but using the variable afterwards, take care" or "hey, it looks like you are only using this argument as a reference, consider not passing it by value" just pop up next to the offending line ; when compared to an IDE-less workflow I pretty much divide the amount of hitting "build" I n…

I get those exact same warnings in Vim :)

Post by mcguire » Sat, Aug 21, 2021, 5:52 PM UTC

schipplock wrote: post #33

> Some Projects with 40000+ files might take >5 minutes to load. I would buy a more powerful computer. I have a project with 34908 files and IntelliJ doesn't care. Not quite 40_000+ files but still a lot :). Also with IntelliJ I make fewer mistakes. This "thing" is just more intelligent than I am. Add "SonarLint" to the game and I sometimes don't even know _why_ I am wrong :P. Also I think "Avoid IDE lock-in of your…

Post by squarefoot » Sat, Aug 21, 2021, 5:57 PM UTC

jeffeld wrote: post #194

bccdee wrote: post #165

Earlier quoted context omitted.

The thing I hate most about IDEs is when they insinuate themselves into a project's development workflow so deeply that you can't make do without them. Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter? Is there so much boilerplate or X…

"An IDE can be a powerful abstraction, but when the underlying layer it's abstracting over becomes inaccessible, then all it's doing is adding more complexity by obscuring concrete details" This. All day long.

Post by szatkus » Sat, Aug 21, 2021, 6:02 PM UTC

rzwitserloot wrote: post #201

bccdee wrote: post #165

Earlier quoted context omitted.

The thing I hate most about IDEs is when they insinuate themselves into a project's development workflow so deeply that you can't make do without them. Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter? Is there so much boilerplate or X…

> Do I have to spin up a whole session of the IDE just to run my test suite? In the java ecosystem at least, the answer is no. But in highly CI-based situations, the answer is still no, but you DO need the CI system to be up, and the only way to run a test at all is to just commit something and see the CI system run it, e.g. because the tests require a database engine that isn't installed on your development machine.…

Post by bootlooped » Sat, Aug 21, 2021, 6:04 PM UTC

rhn_mk1 wrote: post #65

bootlooped wrote: post #36

There is a common perception with electric bicycles that the rider will pedal less hard to go the same speed. But there is an alternative: they could pedal the same amount and go faster. I kind of view IDEs like that. You can use it as a crutch, or you can take the energy you would have used thinking about the things the IDE is now doing for you and focus it elsewhere.

> they could pedal the same amount and go faster Nitpicking, but in the world of regulations, electric assist tapers off until around 25-30 km/h, at which point you start carrying the entire bike anyway, plus the dead weight of the battery and the motor. I wonder if this simile could be extended to programming. Being hindered by not being able to choose your own tools?