What I like about this session is Sam & Pavel really made it very engaging ... and for chrome dev tools..."hats off" ! Although, I'm firebug fan, I use chrome dev-tools for almost every site I visit :)
The technique you mentioned at 45 mins, tree(three) technique I believe its called. Where can I find info on this? Is this a generic memory profiling technique or specific to chrome tools?
Using webtools to debug webtools: 10 for geeky coolness, but maybe a bad idea, since a better boring example would enable to concentrate on the theme. [but don't feel bad, rms made this mistake in the gdb tutorial, made it unnecessary complicated by talking about m4 :-) ]
What I like about this session is Sam & Pavel really made it very engaging ... and for chrome dev tools..."hats off" ! Although, I'm firebug fan, I use chrome dev-tools for almost every site I visit :)
The technique you mentioned at 45 mins, tree(three) technique I believe its called. Where can I find info on this? Is this a generic memory profiling technique or specific to chrome tools?
Great stuff - I know why I use Google for web debugging! :)
What happened to the search option? It's been gone for over a month.
How are you vertically tiling dev inspector frames, ie 35:42?
Using webtools to debug webtools: 10 for geeky coolness, but maybe a bad idea, since a better boring example would enable to concentrate on the theme. [but don't feel bad, rms made this mistake in the gdb tutorial, made it unnecessary complicated by talking about m4 :-) ]
You can get it here: github.com/NV/chrome-devtools-autosave
goog
इस को देखै.
3rd
Why is this video so dim and foggy?
Linux...