Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome DevTools in 2016 and Beyond

developers.google.com

Post reply on HN
Print view View original

41–50 of 59 posts

Re: Chrome DevTools in 2016 and Beyond

#41

Post by Sylos »

jshevek wrote: post #21
kylec wrote: post #9

Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.

I'm glad these folks spend their time on Chrome dev tools rather than catering to the users of inferior browsers who expect people to invest extra energy catering to their preferences. Edit: This may help: https://www.mozilla.org/en-US/firefox/new/

How can you seriously think that Google developers not supporting other browsers than Chrome is ever a good thing? We are already headed quickly enough towards a Chrome monopoly and Google abusing their dominant position on the internet to make other browsers look bad isn't making that any better.

Re: Chrome DevTools in 2016 and Beyond

#42

Post by k3n »

z3t4 wrote: post #40

NodeJS and Chromium have complete different debugging API's. It would be cool if they where the same, so you could reuse the debugging tools on both platforms.

> Thanks to the V8, DevTools, and Google Cloud Platform for Node.js teams, you can now use all of DevTools’ powerful debugging features to introspect a Node.js app.

See also:

https://github.com/nodejs/node/pull/6792

Re: Chrome DevTools in 2016 and Beyond

#43

Post by Flow »

billions wrote: post #37

After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge…

Many news sites insist on Flash still. The shitty thing is that if you use the Developer menu in Safari and change user agent to iPad Safari they often play the video using html5.

Re: Chrome DevTools in 2016 and Beyond

#44

Post by cel1ne »

billions wrote: post #37

After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge…

Is the profiler still tracing instead of sampling?

I once lost a day optimising frequently called JS-methods only to realise that the profiler caused the time spent there.

Re: Chrome DevTools in 2016 and Beyond

#46

Post by kinlan »

kylec wrote: post #33
jshevek wrote: post #26

Earlier quoted context omitted.

Rarely is any description 'needed', but in this case it is 'helpful'. The parent seems to be unaware that Safari has, over time, become inferior (relative to the other popular browsers) increasing the likelihood that the problem is with safari rather than with the site. Being unaware of the inferiority of safari, he didn't even try another browser. Simply knowing that its a safari bug may not be sufficient to maximiz…

You certainly have made a lot of assumptions about me. I did test in other browsers - Chrome, obviously, and Firefox. But the fact that it works in Chrome and Firefox doesn't excuse the fact that it doesn't work in Safari. I'm a web developer, so it's my job to make things work correctly in all the browsers, Safari included, so from my perspective the creator of the page did a bad job. Worse, it wasn't something fanc…

We will be fixing it. It was a bug in Material Design Lite and we need to upgrade.

Re: Chrome DevTools in 2016 and Beyond

#47

Post by drinchev »

billions wrote: post #37

After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge…

I switched to Safari 2 months ago for the same reasons as you did. Definitely feels better speed-wise. Also with iCloud keychain I decreased 1Password usage.

For development though, I still can't get use to Safari's developer tools.

Re: Chrome DevTools in 2016 and Beyond

#48

Post by sjclemmy »

I'm glad to see Css source diffs in there. My workflow consists of tweaking Css in dev tools and then updating source. I've found that if I map directly so Devtools updates the source file I get lost very quickly. Incidentally I'd be interested in knowing of better ways of writing / debugging css.

Re: Chrome DevTools in 2016 and Beyond

#49

Post by jayflux »

Flow wrote: post #43
billions wrote: post #37

After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge…

Many news sites insist on Flash still. The shitty thing is that if you use the Developer menu in Safari and change user agent to iPad Safari they often play the video using html5.

That's by design. Please read the "Are you planning to add support for Safari on Mac OS X?" bit on http://www.bbc.co.uk/blogs/internet/entries/8be5501d-43e7-4b...

Re: Chrome DevTools in 2016 and Beyond

#50

Post by kinlan »

kylec wrote: post #9

Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.

We will be fixing this. There was a change in safari that busted our material design lite usage.
Post reply on HN