xzyfer

5 ms·

1.
Sass and Browser Compatibility(blog.sass-lang.com)
1 points by xzyfer 10y ago|0 comments
2.
by xzyfer 10y ago
It's hard to say for sure. Server implementations can vary wildly, make sure to test any implementation closely. I know from talking to CloudFlare that their implementation respects browser hints. Their implementation is also open sour
3.
by xzyfer 10y ago
I'm out y'all. Thanks for all the support. Feel free to follow up on Twitter at @xzyfer
4.
by xzyfer 10y ago
The priority queue isn't the issue. In fact the priority queue is what kept our first paint times tanking because browsers prioritised render blocking resources instead of images. The issue was due to the variance of image size. An ima
5.
by xzyfer 10y ago
The priority queue isn't the issue. In fact the priority queue is what kept our first paint times tanking because browsers prioritised render blocking resources instead of images. The issue was due to the variance of image size. An ima
6.
by xzyfer 10y ago
Browser do currently do this. H2 has two types of prioritisations: weighted, and dependency. All browsers implement weighted resource prioritisation and weigh resources by content type. This is a hold over from what they do for HTTP/1
7.
by xzyfer 10y ago
You read it correct. By not moving our render blocking assets like CSS, JS and fonts over to the http/2 we rule out performance changes due to improvements to head of line block. Our images were always on a separate hostname so the DNS
8.
by xzyfer 10y ago
This is correct. Visually completion will not be achieved until the entirety of the images within the viewport are downloaded. However progressive jpegs could improve initial paint times. These are dynamic so each page would have it's
9.
by xzyfer 10y ago
To the best of my knowledge you are correct about how CloudFlare works. For context this data was collected over the period about a month on real production pages with significant traffic. The edges were well and truely primed.
10.
by xzyfer 10y ago
Thanks mate, glad you enjoyed it.
11.
by xzyfer 10y ago
Totally. There are a bunch of ways to address the performance issue. As I alluded to at the end of the post there serious technology considerations when preprocessing so much image data. We're currently looking at whether we can solve
12.
by xzyfer 10y ago
H2's single long lived connection means it's a contender to replace websockets. As a bonus you get to use HTTP semantics.
13.
by xzyfer 10y ago
Server push at the edge is problem atm. Current push semantics require the HTML document say which resources to push. That's an issue if you're serving assets off a CDN domain. Asset domains make less since with h2 from a performa
14.
by xzyfer 10y ago
There are discussions happening on how browsers can allow authors to resource prioritisation hints. I'm curious to see where it goes. We'd ideally like to be able to say – "prioritise 10 images in the viewport". You hack
15.
by xzyfer 10y ago
Thanks mate, really appreciate it.
16.
by xzyfer 10y ago
Hey all, I'm the author of that blog post. I'll be floating around for a while, happy to answer any questions.
17.
by xzyfer 11y ago
I've thought about this also. Alternatively some mixed format file like yaml front matter style.
18.
Libsass 3.2.0 released. Biggest release to date(github.com)
2 points by xzyfer 11y ago|0 comments
19.
CSSConf comes to Australia for the first time(cssconf.com.au)
2 points by xzyfer 13y ago|0 comments
20.
by xzyfer 13y ago
Almost like it puts cats on you
21.
by xzyfer 13y ago
Had a power nap, and now I'm back. Your feedback has been awesome
22.
by xzyfer 13y ago
Awesome list dude!
23.
by xzyfer 13y ago
I hate to break it to you, I'm a Lakers man :) I'd make the trek to Staples. Added Sunday Street fests though :)
24.
by xzyfer 13y ago
You had me at "Damn, you are going to be very drunk and full after completing my list". Love this btw. I'll give it a proper look over at a saner hour (it's 5am here). I'm curious what the law are around hitching a tow from a cable car on m
25.
by xzyfer 13y ago
Don't mind if I do :) https://github.com/xzyfer/us-travel-checklist/commit/7ca2239...
26.
by xzyfer 13y ago
I'm more of a Lego Land man myself :)
27.
by xzyfer 13y ago
This was interesting. Thanks.
28.
by xzyfer 13y ago
I don't see how it's any different from a gist. By using Github I've intentionally limited my audience.
29.
by xzyfer 13y ago
I felt like that would be mayhem to manage, and curate. I'm trying to curate a list of unique, individual experiences.
30.
by xzyfer 13y ago
I like your idea though. Lunch is on me! https://github.com/xzyfer/us-travel-checklist/commit/c09178e...

More ›