Login now

Not your profile? Login and get free access to your reports and analysis.

Tags

Sign in

No tag added here yet.
You can login on CircleCount to add some tags here.

Are you missing a tag in the list of available tags? You can suggest new tags here.

Login now

Do you want to see a more detailed chart? Check your settings and define your favorite chart type.

Or click here to get the detailed chart only once.

Nat Duca has been shared in 10 public circles

AuthorFollowersDateUsers in CircleCommentsReshares+1Links
Thomas Power29,643to follow the Google I/O 2012 event over the next few days please use/share this Circle. This event is critical to the development of your knowledge of the Google+ ecosystem and most importantly the G+API.2012-06-27 06:15:011945610CC G+
Scott Knaster5,498version 4 update: Shared circle of Google I/O speakersIf you've already added the previous version of this shared circle, just add +Rich Hyndman and you'll be up to date. That's the only change in this version.Whether you're coming to San Francisco for Google I/O or participating online, there are many ways to keep up. Here's another: follow the I/O speakers by adding this shared circle. #io12  2012-06-27 03:51:201963176CC G+
Christian Kurzke (cnkurzke)8,673WOW, #io12  has not even started yet, and +Google+ is already on fire!If you guys try to stay on top of what's going on here, I'd like to share who I have on "speed dial" here in my "Movers and Shakers" circle.Most of them are Googlers, some of them are speakers, others are helping making stuff happen behind the scenes.All around, a great group of people to follow if you're here at Google IO, or if you're watching and following from home.Remember, most sessions are LIVE broadcast, all other sessions are recorded and available later!Let's ROCK THIS TOWN!(yeah, and follow me for my whacky music selection i'll share with you throughout the week... ;) )2012-06-26 19:22:093147411CC G+
Mano Marks0I'm getting really excited about Google I/O. We have a full set of +Google Maps API sessions. My session in on Wednesday, and will be live streamed. Of course all sessions will be recorded and posted. Here's a shared circle, started by +Scott Knaster of #io12  speakers.2012-06-26 16:39:05194247CC G+
Scott Knaster5,466version 3 update: Shared circle of Google I/O speakersv3: added one +Robert Pufky , removed another +Robert Pufky  (apologies to both), added +Ali Afshar .Whether you're coming to San Francisco for Google I/O or participating online, there are many ways to keep up. Here's another: follow the I/O speakers by adding this shared circle. #io12  2012-06-26 16:01:541951124CC G+
Scott Knaster5,435version 2 update: Shared circle of Google I/O speakersv2: added +Daniel Hermes , removed +danny hermes (apologies to both)Whether you're coming to San Francisco for Google I/O or participating online, there are many ways to keep up. Here's another: follow the I/O speakers by adding this shared circle. #io12  2012-06-25 16:26:241940342CC G+
Hacker News Circle5,697Part 3/3 (Remember to add all of them) Notice: Google+ Shared Circles are snapshots and you must manually re-add from this circle in order to update your circle with new users. Automatically generated from http://hngp.axxim.net/ (Go there to add yourself to the circle) at 01/29/2012 at 12:00pm EST Made by antimatter15 https://plus.google.com/116347431032639424492/aboutSource code (Github): https://github.com/antimatter15/autocircle2012-01-29 17:00:114652733CC G+
Hacker News Circle5,679Part 3/3 (Remember to add all of them) Notice: Google+ Shared Circles are snapshots and you must manually re-add from this circle in order to update your circle with new users. Automatically generated from http://hngp.axxim.net/ (Go there to add yourself to the circle) at 01/23/2012 at 12:00pm EST Made by antimatter15 https://plus.google.com/116347431032639424492/aboutSource code (Github): https://github.com/antimatter15/autocircle2012-01-23 17:00:08423322CC G+
Hacker News Circle5,667Part 3/3 (Remember to add all of them) Notice: Google+ Shared Circles are snapshots and you must manually re-add from this circle in order to update your circle with new users. Automatically generated from http://hngp.axxim.net/ (Go there to add yourself to the circle) at 01/17/2012 at 12:00pm EST Made by antimatter15 https://plus.google.com/116347431032639424492/aboutSource code (Github): https://github.com/antimatter15/autocircle2012-01-17 17:00:06303001CC G+
Hacker News Circle5,667Part 3/3 (Remember to add all of them) Notice: Google+ Shared Circles are snapshots and you must manually re-add from this circle in order to update your circle with new users. Automatically generated from http://hngp.axxim.net/ (Go there to add yourself to the circle) at 01/17/2012 at 12:00am EST Made by antimatter15 https://plus.google.com/116347431032639424492/aboutSource code (Github): https://github.com/antimatter15/autocircle2012-01-17 05:00:06291000CC G+


Activity

Average numbers for the latest posts (max. 50 posts, posted within the last 4 weeks)

13
comments per post
13
reshares per post
23
+1's per post

5,362
characters per posting

Latest posts

2014-03-31 23:52:24 (13 comments, 13 reshares, 23 +1s)

I'd like to soapbox about the need for rationality in the web platform, using position:sticky as a guinea-pig to explain my perspective.

The thing that bugs me about position:sticky is that is entangled with the magical nature of scrolling on the web. Per spec, the browser can scroll the page up and down without telling JS: you get a scroll event, but it happens after the scroll has actually happened.

Wat.

Here's the thing: this ability in browsers is super important, because scrolling is super duper important to get right for users. Without it, going to espn.com and scrolling is a really horrible user experience. On mobile, that poor site janks for a half second while it loads. I NEED MY SPORTS SCORES TO SCROLL AT 60FPS. The browser works around this by making scroll asynchronous. A simpler example is this: http://jankfree.org/examples/simple_jank.html : on mobile... more »

2014-01-07 02:31:00 (0 comments, 0 reshares, 0 +1s)

The one where I ruminate of layers, platforms, cabbages, and kings.

cross-posting from blink-dev

posted image

2013-12-17 17:58:51 (0 comments, 0 reshares, 0 +1s)

The Runtime Performance Checklist

A consolidation of the big hitters that will kill your fps.

Have you checked them all off?

2013-11-26 05:09:06 (0 comments, 0 reshares, 3 +1s)

Scrolling at 60fps

For a while people recommended to use a "noHover" class during scrolling to avoids paints that kill 60fps. Turns out that doesn't actually work because adding the noHover class causes a full style recalc which will likely completely annihilate your frame rate.

Today I saw this article, which tries to use pointer events instead to avoid the problems http://www.thecssninja.com/javascript/pointer-events-60fps
… and, indeed, it achieves great frame rates. Unfortunately it is even more broken, since it will block all clicks on your site within half a second after you stop scrolling. That might be quiet a few clicks. Fortunately we have found a way to avoid those problem:

The key insight is to use a cover div on which you toggle pointer events (or you just move it in and out of view using translate during scrolling). Then, when theus... more »

posted image

2013-11-07 19:47:10 (0 comments, 5 reshares, 8 +1s)

Thanks to +Paul Lewis,  http://jankfree.org/ now has an RSS feed. Good way to follow along if you're trying to keep up with the ever-changing world of silky smooth web design.

posted image

2013-11-07 16:04:29 (0 comments, 1 reshares, 3 +1s)

High performance animations

Details: http://www.html5rocks.com/en/tutorials/speed/high-performance-animations/

TL;DR Most modern browsers can animate these four properties cheaply. If you animate anything else chances are you'll bust your frame budget and miss out on 60fps.

#perfmatters

posted image

2013-11-05 08:42:18 (2 comments, 0 reshares, 2 +1s)

The best way to avoid the dreaded 300ms click delay is to disable double-tap zoom.

Much has been written about the evil 300ms delay in dispatching click events on touch-based browsers (eg. https://developers.google.com/mobile/articles/fast_buttons).  There are some good libraries for dealing with this (notably https://github.com/ftlabs/fastclick), but they have drawbacks such as:
- They can significantly hurt scrolling performance (https://plus.google.com/+RickByers/posts/cmzrtyBYPQc)
- They disable touch adjustment (the process of 'fuzzing' the position of a touch to a nearby target to make it easier to hit small targets)
- There are number of edge cases that are hard to get right in all browsers that can lead to bugs and confusion.

It's much better to avoid the problem entirely if possible.  Most modern browsers have a mitigation that manyde... more »

posted image

2013-11-01 01:53:02 (0 comments, 0 reshares, 4 +1s)

Android's WebView is now powered by Chrome

The latest release of Android (KitKat) now uses a Chromium based WebView for embedded web content across the system.  The new Chromium based WebView lets you take advantage of many of the latest features inside Chrome for your applications and content, including first class support for Chrome DevTools.

Check out our docs about the latest changes to WebView https://developers.google.com/chrome/mobile/docs/webview/overview 

posted image

2013-10-31 02:35:30 (0 comments, 0 reshares, 2 +1s)

A Developer's Guide to Rendering Performance

Where I run through how pixels get to the screen, what tools Chrome provides for you to profile your projects, and how to pronounce GIF correctly.

Educational, yo.

2013-10-07 23:52:39 (3 comments, 0 reshares, 2 +1s)

<rant>Beware of Applecare: as I learned from the lovely Palo Alto Apple Store today, quoting, at "even a small drop of water contact," Apple can decline service on everything. In a world where laptops and things like trackpads get little drops of water on them as a course of life, this renders AppleCare nullable virtually without thought on the part of Apple. Save yourself $249.</rant>

posted image

2013-10-02 18:06:05 (2 comments, 2 reshares, 15 +1s)

60 frames per seconds all the things!
Video of +Nat Duca's  *"Advanced Jank Busting in Chrome"*
http://2013.jsconf.eu/speakers/tom-wiltzius-and-nat-duca-advanced-jank-busting-in-chrome.html?1

posted image

2013-08-30 15:37:43 (6 comments, 1 reshares, 9 +1s)

More jank-busting info from +Tom Wiltzius and I.

posted image

2013-07-25 03:24:02 (0 comments, 0 reshares, 6 +1s)

Dear Diary,

An exciting day today - my patch for mouse controls in chrome://tracing landed in Canary! You can use the mouse to pan around (+ shift to temporarily switch to selection, + cmd / ctrl to temporarily switch to zoom)

LGTM.

Paul

2013-07-24 05:12:07 (0 comments, 0 reshares, 0 +1s)

I did a quick presentation today on about:tracing for Chrome engineers, and you might like it too. About:tracing is like devtools on steroids. I don't yet recommend about:tracing for regular web developers (sometimes it 'roid rages) but it's a great addition to your toolbox if you want to dive into performance.

This builds on the work by Nat Duca and Tom Wiltzius in their I/O talk "Jank Free: Chrome Rendering Performance": Google I/O 2013 - Jank Free: Chrome Rendering Performance

posted image

2013-07-19 03:01:29 (0 comments, 0 reshares, 2 +1s)

Reminder: With Chrome DevTools open, using the "debugger" statement in JavaScript will stop execution & jump into the interactive debugger. Useful for setting fixed breakpoints in code.

posted image

2013-05-31 15:25:25 (0 comments, 0 reshares, 2 +1s)

Chrome Canary gets a new tracing feature allowing you to record paints through the life of a page & examine gpu layering Tracing paint operations in Chrome Canary

posted image

2013-05-28 18:14:31 (0 comments, 0 reshares, 3 +1s)

Changing the performance conversation

I spent a lot of time discussing performance with developers at Google I/O. I noticed that the emphasis is still heavily in favour of network and page load time which, while critical, isn't the only concern we have. I've written up a few thoughts on my blog: http://aerotwist.com/blog/reflections-on-performance-at-google-io/

#perfmatters  

posted image

2013-05-20 19:32:16 (0 comments, 106 reshares, 15 +1s)

+Tom Wiltzius and I gave a talk last week at I/O about fighting web page jank in Chrome. For slides from the video, as well as other jank busting resources, wander on over to http://jankfree.org/.

If you're fighting with rendering performance in a web app, feel free to give a shout.

#perfmatters  #GoogleIO2013 #jankfree

posted image

2013-04-05 05:59:09 (0 comments, 0 reshares, 3 +1s)

#protip : Your code can use console.time() & console.timeEnd() to mark ranges in DevTools Timeline recordings. Combine with console.timeStamp() for annotations and you have SO much profiling power.

posted image

2013-04-04 21:29:00 (14 comments, 69 reshares, 56 +1s)

The question has come up a few times lately, "What are the transparent bars in Chrome DevTools' timeline?"

The short version is that a hollow frame means one of two things: your javascript main thread was busy doing other stuff that we forgot to show in DevTools [oops!], or you were bottlenecked on your GPU.

To tell the difference, you want to enable "Timeline: Show CPU Activity on the Ruler" inside DevTools' settings. Then, look for little dark grey blocks on the "Records" row... see them? Those are dark when the renderer thread was busy. If the renderer thread is mostly idle, e.g. no dark block, as is the case the screenshot from Dan that I yanked for this post, it is a very good signal that you are GPU bound.

GPU boundedness typically comes from two things:
1. having -webkit-filter, preserves3D properties on elements. Those eat... more »

posted image

2012-06-29 05:00:24 (8 comments, 2 reshares, 22 +1s)

Fighting web page jank, with about:tracing, at Velocity 2012. :)

Lets make the web #jankfree.

Buttons

A special service of CircleCount.com is the following button.

The button shows the number of followers you have directly in a small button. You can add this button to your website, like the +1-Button of Google or the Like-Button of Facebook.






You can add this button directly in your website. For more information about the CircleCount Buttons and the description how to add them to another page click here.

Nat Duca