inian

15 ms·

151.
RequestAnimationFrame Scheduling for Nerds(medium.com)
2 points by inian 10y ago|0 comments
152.
Chrome introduces a new way to enable experimentation with new web APIs(github.com)
5 points by inian 10y ago|0 comments
153.
XSS-es in Google Caja(blog.bentkowski.info)
1 points by inian 10y ago|0 comments
154.
Gzip is not enough (2013)[video](youtube.com)
2 points by inian 10y ago|0 comments
155.
The State of the W3C Web Performance Working Group [video](youtube.com)
1 points by inian 10y ago|0 comments
156.
Progressive Web Apps in Firefox(blog.wanderview.com)
2 points by inian 10y ago|0 comments
157.
New Performance Metrics for Progressive Web Apps(docs.google.com)
3 points by inian 10y ago|0 comments
158.
by inian 10y ago
Hey guys, This is Inian from the Dexecure team. We want to build tools to make it super simple for developers to build a fast performing website across different browsers and devices. New features that can speed up websites are being develo
159.
Show HN: Dexecure – Optimize images in your webpage with a single line of code(dexecure.com)
31 points by inian 10y ago|2 comments
160.
by inian 10y ago
Part of this problem is solved via the Client Hints spec ( http://httpwg.org/http-extensions/client-hints.html#save-dat... ) When the user turns this on in his preferences, Chrome sends this data to the server as a head
161.
by inian 11y ago
Definitely not. Page load (thats the time the browser spinner stops spinning), first render, etc. are slightly better metrics. But even page load time and first render times aren't without their own problems. Resources loaded asynchron
162.
by inian 11y ago
The DOM Content loaded in this test is 157 ms. WPT uses a confusing terminology when it comes to this (Document complete time != Dom content loaded time) True it is not the same as the 65ms claimed in the article but its not that far off to
163.
by inian 11y ago
Oh thats why the dev build of React was there in the page. Makes sense!
164.
by inian 11y ago
A few points - 1. A direct comparison to Facebook's react Github page may not be fair. Their page is 10 times heavier than the blog page - of course its going to be faster. 2. Actually the Facebook's React page is not that well de
165.
by inian 11y ago
yup pretty much. We managed to report and fix some bugs though. But it is pretty hard to get the point of contact person for some websites.
166.
by inian 11y ago
We conducted a similar experiment on the top 1000 websites and found 820 unique DOM-Based XSS vulnerabilities in these sites! You can find out more about our techniques in our paper here http://www.comp.nus.edu.sg/~enricob&#