3 ms·
Great point. Many devs won't touch a tech stack that doesn't have tons of tooling and lots of ceremony possible. (To those used to such things, you will find s
by pnathan 12y ago
Great point. Many devs won't touch a tech stack that doesn't have tons of tooling and lots of ceremony possible.
(To those used to such things, you will find something tremendously freeing if you drop down to using no language specific tools but the compiler/interpreter).
- izacus 12y agoThat's because we mostly know just how much time and frustration a good debugging (note: not editing!) toolchain saves. There's a huge difference using IDEA with it's integrated debugger to for example, typing everything out manually in GDB. And here Scala isn't any different - it's noticably easier and takes way less time to debug a complex piece of software since we have good IDEA integration. And that's what most of people bashing IDE's don't get: it's the ease debugging that's important, not typing code!
- pnathan 12y agoHonestly, I've seen people who swore by their IDEs and paired with them... usually what was going on is they were writing code they literally did not understand, and used the IDE as a lever to help them get by without understanding. IDEs simply allowed them to write very bad systems without any conceptual integrity, and they did. Which wasn't my original point really.
- michaelochurch 12y agoPersonally, I'm a believer in the concept of a read-only IDE. Sometimes code visualization becomes easier with a GUI. I'll grant that. Likewise, IDEs can make debugging easier. Writing of code with an IDE has the problems you discussed.