9
Comments
  • 1
    Is there another way?
  • 2
    @N00bPancakes Chrome or VSCode's debugger, breakpoints wherever you need them, and when execution stops, you just inspect the context instead of logging it; also direct log points instead of breakpoints. Still, nothing wrong with console log as long as you don't forget extraneous logs after you're done with them. Whatever works for you - a console log might be more indicative i.e. if you suspect a method is called more times that needed.
  • 3
    @kamen I know. I was being silly. ;)
  • 1
    Unless I need to debug some more heavy logic (which there usually aren't), I don't like the idea of stopping mid-execution. (mostly because of hot reloading) Just run the damn thing and log out the results for me, you can even use tools in order to label and color code stuff.
  • 4
    @N00bPancakes no, debuggers are for heretics and simps, console.log is da wae
  • 3
    @neeno mah man 😅👏
  • 1
    @neeno

    They don't think it be like it is but it do.
  • 1
    i use alert() 😂
  • 1
    @linus-torvald lol what a coincidence. I was just watching Linus Torvald saying "fuck u" to Nvidia. 😅 lmao
  • 1
    This page
  • 0
    @bug123 Lolwut you're right. Normally not only should the comments be removed, but also the code minified.
Add Comment