3 ms·

If you could explain or show how you connected VS code to act as the debugger for Chrome I would let you and you could use VS code instead. I would also be impr

by 0xfeba 8y ago

If you could explain or show how you connected VS code to act as the debugger for Chrome I would let you and you could use VS code instead. I would also be impressed. I didn't mean to imply they had to use Chrome.

Merad 8y ago
> I would also be impressed. There's nothing to it, most people just apparently don't know that it's possible. Chrome, Firefox, and I assume all the major browsers support remote debugging, your IDE just need to know how to send them commands. All you need to do is install the Chrome/FF debugging plugin and click 'Start Debugging'. A settings file should open for you to configure the url to launch.
- tchaffee 8y ago
  There are some details though. If you are using webpack you need to use the right 'devtool' settings to get the source line numbers to match up.
- 0xfeba 8y ago
  That's a lot more effort than lots of people bother with. At least, from the pool of people we interview. But I have no say in that.
tchaffee 8y ago
How would I do that when I was handed your laptop? I would assume that's part of the constraints and revert to console.log, like I usually do when it's not my laptop. Good interviews are hard to design. You have to be super careful that you are testing for what you really think you are. I've let people use their own laptop, search for answers, use StackOverflow, and ask me questions. Just like we all do in real life.
nojvek 8y ago
I’m one of the contributors to VScode chrome debug. If someone used vscode to debug chrome in an interview and explained how the debugger itself is a dumb extension that translates JSON RPC based vscode debug protocol to JSON rpc based chrome remote protocol under the hood, I would be super duper impressed. Although console.log isn’t a terrible debugging strategy. My first thing to learn in any language is how to do a printf

by 0xfeba 8y ago

Merad 8y ago

> I would also be impressed. There's nothing to it, most people just apparently don't know that it's possible. Chrome, Firefox, and I assume all the major browsers support remote debugging, your IDE just need to know how to send them commands. All you need to do is install the Chrome/FF debugging plugin and click 'Start Debugging'. A settings file should open for you to configure the url to launch.

tchaffee 8y ago
There are some details though. If you are using webpack you need to use the right 'devtool' settings to get the source line numbers to match up.
0xfeba 8y ago
That's a lot more effort than lots of people bother with. At least, from the pool of people we interview. But I have no say in that.

tchaffee 8y ago

How would I do that when I was handed your laptop? I would assume that's part of the constraints and revert to console.log, like I usually do when it's not my laptop. Good interviews are hard to design. You have to be super careful that you are testing for what you really think you are. I've let people use their own laptop, search for answers, use StackOverflow, and ask me questions. Just like we all do in real life.

nojvek 8y ago

I’m one of the contributors to VScode chrome debug. If someone used vscode to debug chrome in an interview and explained how the debugger itself is a dumb extension that translates JSON RPC based vscode debug protocol to JSON rpc based chrome remote protocol under the hood, I would be super duper impressed. Although console.log isn’t a terrible debugging strategy. My first thing to learn in any language is how to do a printf