3 ms·
Coming from a Node.js background, I use a text editor, and debug with Chrome using node-inspector. In other languages (Ruby, Elixir, Clojure), I just debug wit
by notduncansmith 12y ago
Coming from a Node.js background, I use a text editor, and debug with Chrome using node-inspector. In other languages (Ruby, Elixir, Clojure), I just debug with print (and make heavy use of the REPL).
As for buttons vs commands, I suspect that's largely a preference thing (believe me, I thought hard about refuting the buttons because I personally dislike them, but eh, different strokes). I have shell aliases for most of my common commands, and if something needs to run continuously or on save, it's pretty easy to write a script or Gulpfile that'll do that for me. For anything else, it's uncommon enough that it'd be a menu item (hopefully!) anyways, not a button, so I'm unlikely to see any effort savings from using an IDE vs the terminal.
- collyw 12y agoYes, I have a few shell aliases for commands with a load of parameters I use. I suppose setting up Eclipse versus writing a few aliases is probably about equivalent. Debugging with print can only get you so far. I use Django which is a big framework, so I couldn't understand the code without a proper step through debugger. I would say its been essential to get to the understanding I have now of forms and class based views.
- notduncansmith 12y agoI agree. Beyond the preference aspect there's definitely a notion of using the right tool for the job - and in an unfamiliar codebase (e.g. one that relies on a heavy framework like Django filled with thousands of lines of code I've never seen), as I mentioned before an IDE can be of significant benefit. That said, once one has grokked the framework to a fair degree, I would imagine that continuing benefit (in that respect) would be quite limited.