Summary: 1. Better side menu in source pannel, resizable 2. More ES6 Support like arrow functions 3. multiline editing with functions in console 4. array[2]. now will do auto completion just like obj. does 5. inline debugging capability instead of just perline breakpoint 6. drag and drop work folder instead of creating workspace then edit css/js right in browser 7. ability to find unused css via recording in timeline > css coverage, then interact and stop recording. Unused will be highlighted. 8. start node --inspect url and connect without opening url, right from console using frame select option. 9. Bunch of Progressive Web Apps stuff you don't care about right now 10. Lighthouse aka page speed is built into chrome.
You da man, Paul! Please tell your team that we RUclipsrs appreciate their great work! lastly, I like your management technique to build a web app to know where Sam is on his daily commute.
loved the video alot. The one thing that I liked about you Paul is simply annotating the big things into small . hats off. one day will be part of your team Paul .
I clicked through to 1) congratulate the good presentation and 2) provide the feedback that whoever edited this keeps cutting to Paul Irish right when you need to see what's on screen. Can we get some technically savvy camera folks next time so they know when it's appropriate to show his face? Kind of defeats the purpose otherwise.
I've got here after clicking on What's New link for Workspaces 2.0. I'm on Chrome 63.0.3239.132, but I still can't make Workspace working even for just local CSS and HTML file. What am I doing wrong?
Jesssseeee... why the guy take away the screen while he is showing the stuff.. I literally lost few very important things, because there is someone that does not know what they are doing when editing the video...
In Case anyone else wonders how to enable those experimental features in canary.. developers.google.com/web/tools/chrome-devtools/settings (In the Enable Experiments section)
Ugh. The "automagic find all your files" "how it works is really complicated I won't even talk about it" workspaces 2.0 feature explained starting 14:28 broke my entire dev workflow. It doesn't find my local stylesheets and scripts correctly (even though they're a simple flat folder that matches the network structure) and now that it's "magic" there's now no option to "map to file system resource" like before. Really frustrating when programmers break the tools you rely on. If Microsoft Office Autoformat and Clippy was any indication: software that tries to guess what you want to do and eliminates manual options almost always ends up getting it wrong and becoming more frustrating to use the end.
Update: got this finally working by dumping Chrome's cache. Somehow it was holding onto network files too long despite max-age=0 and then missing the mapping.
Pour une vidéo de démonstration on s'en fou un peu de voir le publique applaudir on préférerai voir constamment le code changer ;) Mais merci pour cette trés bonne vidéo ! ^^
16:56 I'd appreciate if you actually did attempt to explain how. Somewhere. Anywhere. Calling it magic doesn't help us debug WHY it isn't working for those of us not blessed enough to have it work automatically.
2016 and interlaced video is not dead yet. Nice.
The interlacing effect is only present in 1080p, so may be they are just encoding artifacts, not actual interlacing.
Maybe the original video before YT processing was "1080i" so .. It must have been mushed below 720p and such, while evident on 1080p.
Amazing content, but panning away from the screen while a demo is happening is quite annoying : (
It pretty much ruins the educational value of the most critical moments!
Just going to take this folder and drop it here....
STOP. CUTTING. AWAY.
Summary:
1. Better side menu in source pannel, resizable
2. More ES6 Support like arrow functions
3. multiline editing with functions in console
4. array[2]. now will do auto completion just like obj. does
5. inline debugging capability instead of just perline breakpoint
6. drag and drop work folder instead of creating workspace then edit css/js right in browser
7. ability to find unused css via recording in timeline > css coverage, then interact and stop recording. Unused will be highlighted.
8. start node --inspect url and connect without opening url, right from console using frame select option.
9. Bunch of Progressive Web Apps stuff you don't care about right now
10. Lighthouse aka page speed is built into chrome.
Every year I wait dev summit only for this part with dev tools :)
Excellent stuff Paul! All the important updates of devtools in 30min :) very cool!
This guy is one my favourite speakers
You da man, Paul! Please tell your team that we RUclipsrs appreciate their great work! lastly, I like your management technique to build a web app to know where Sam is on his daily commute.
loved the video alot. The one thing that I liked about you Paul is simply annotating the big things into small . hats off. one day will be part of your team Paul .
inline breakpoint is awesome!
That's a life changer!
"problems are good", this guy is awesome!
There is some article or documentation about accuracy, validity or reliability of Chrome DevTools?
I clicked through to 1) congratulate the good presentation and 2) provide the feedback that whoever edited this keeps cutting to Paul Irish right when you need to see what's on screen. Can we get some technically savvy camera folks next time so they know when it's appropriate to show his face? Kind of defeats the purpose otherwise.
Reallu love Paul. He is my inspiration developer!
i love this guy.... the thought process sounds exactly like mine when coding hahaha... we're all a lil silly
Is there a version of this where it doesn't pan away from the screen at critical moments?
4 people didn't open DevTools
Ok, Chrome 55 is out, but it seems this css coverage-tool isnt included yet?! Cant find it - just in Chromium?
amazing new features
How to get the watch window, call stack etc. at the bottom of the screen? On Win 10 it's on the right side. Can we move it down??
nice presentation. I'd love to see cold folding in sources.
so nice, precise moment when he links folders and the video goes to his face... please show the console!
I've got here after clicking on What's New link for Workspaces 2.0. I'm on Chrome 63.0.3239.132, but I still can't make Workspace working even for just local CSS and HTML file.
What am I doing wrong?
Had to rate down just because of the camera. A demo doesn't work if I can't see what's happening
08:48 snippet 15:11 mapping, sources, workspace
Anyone get the workspace persistence to work? Is it only in chromium or Canary? I've had no luck getting it to work.
Jesssseeee... why the guy take away the screen while he is showing the stuff.. I literally lost few very important things, because there is someone that does not know what they are doing when editing the video...
6:12 Safari cred. I like it.
Which version of Chrome this is going to be?
this also confuse me quite a little bit, after I download & install the chromium, I found the new features were there.
I don't know why but I check both Chrome Canary and Chromium and didn't see the features.
On Canary I had some of the features. Unfortunately not all of them.
Grzegorz Bielak
In Case anyone else wonders how to enable those experimental features in canary.. developers.google.com/web/tools/chrome-devtools/settings (In the Enable Experiments section)
Nice!
is there a way to debug Node apps running on a remote server? (I guess that would require SSH, SFTP implemented within Chrome so probably not)
Luke Moll you can use x11 forwarding
I assume you don't just need an ssh/sftp terminal connection from the browser, which can be done with the Chrome SSH Extension.
No puedo realizar "custom mapping" ahora en workspaces 2.0 :(
Would love if changes to a source file would persist after page reload. If on reload, Chrome would use the local mapped file.
My friends were setting this up with Charles Proxy yesterday
Yeah, that's (Charles) what I'm using as well!
As of ~2018, this is possible with 'Local Overrides'.
Ugh. The "automagic find all your files" "how it works is really complicated I won't even talk about it" workspaces 2.0 feature explained starting 14:28 broke my entire dev workflow. It doesn't find my local stylesheets and scripts correctly (even though they're a simple flat folder that matches the network structure) and now that it's "magic" there's now no option to "map to file system resource" like before. Really frustrating when programmers break the tools you rely on.
If Microsoft Office Autoformat and Clippy was any indication: software that tries to guess what you want to do and eliminates manual options almost always ends up getting it wrong and becoming more frustrating to use the end.
Update: got this finally working by dumping Chrome's cache. Somehow it was holding onto network files too long despite max-age=0 and then missing the mapping.
Paul is growing old too quickly! Great talk! Thank you.
I was a youthful 35 when I gave this talk. You should see me now. 🧓
Peace of crap! Now source -> live editing complete broken! Thank you for this mr. i know how to broke things that worked before just perfectly !
Pour une vidéo de démonstration on s'en fou un peu de voir le publique applaudir on préférerai voir constamment le code changer ;) Mais merci pour cette trés bonne vidéo ! ^^
Your my511 api token is visible!
This guy looks like Sherlock Holmes. Investigating JavaScript issues :)
16:56 I'd appreciate if you actually did attempt to explain how. Somewhere. Anywhere. Calling it magic doesn't help us debug WHY it isn't working for those of us not blessed enough to have it work automatically.
"Gotta clap on the 200s" :)
Переведите плиз на Russian Lang
Why can't the cameramen be educated to focus well on the slides throughout the talk. Excellent content but poor coverage !
hm aha uhu aha that's good HA THAT'S GREAT! :D
Come on, stop taking the demo away!
Good content, poor delivery. Sorry Paul but you need to work on your public presentation skills.