Folks, DO NOT STOP using console.log. Stepping through code and logging are two different things, with different use cases. One gives you a few into what's happening at a specific time, the other gives you a view into what's happening over time.https://twitter.com/calebporzio/status/1151185995309690886 …
-
-
e̶x̶e̶c̶u̶t̶i̶o̶n̶ ̶o̶r̶d̶e̶r̶ Actually, in many cases, what we're trying to find out isn't just the point/iteration that a particular line of code was executed, but whether given the runtime state it was reachable at all. `console.log('are we here?')` etc.
-
I think the debugger could be rewritten to be much more useful, but it probably won't be. It is a strangely conservative piece of technology. It might be interesting to see if we could programmatically interface with it to build better debugging tools.
- 1 more reply
New conversation -
-
-
`debugger` statement is useful when debugging transformed code and it's hard to find the place you want to look at in DevTools. Also when debugging on page load or async script load when it loads and executes too fast for you to set a breakpoint.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
STOP USING console.log() in JavaScript. There's something just as easy and WAY more powerful!