3,366 karma · joined March 23, 2009
Still, I like the flexbox-based grid.
Here's a few ways to avoid it: https://gist.github.com/nateberkopec/1184c81a92c10d84d779
Is there anything out there in this realm? If not, why not?
With closed-source/proprietary apps, you're at the mercy of the provider for getting out any data.
ISIS has said they're killing us because of their interpretation of a book written in the first millennia. They say this every time they attack us. Yet (mostly on the left) we keep coming up with reasons why this isn't the case. "No, actually, you're not attacking us for that reason, really it's our fault because we gave the oil to the emirs."
When someone shoots up a Planned Parenthood, however, he doesn't even have to make a public statement and the same people are quick to blame Christian beliefs or rhetoric and immediately accept the ideological reason for the violence. Why don't we say that gunmen attack Planned Parenthoods because of income inequality in the United States?
Finally, is there anywhere to find the original article by Piketty in English? The linked version is in French.
Are there are any "tag bundlers" that work? It seems like such a great idea.
Really, the viewport tag just needs to be before any CSS - external or inlined.
EDIT: Updated the article to mention intranets.
99.5% of websites that use this tag - it does nothing. Internet Explorer users don't set their own Compatibility View settings, so we can ignore that. Second, if you're cool enough to be on Microsoft's Compatibility View list, you're cool enough to know that you need an X-UA-Compatible tag and you know what it should be set to.
The problem I have is people blindly copy-pasting this value from whatever HTML5 boilerplate they got it from. I'm going to rephrase this section of the post to make my point more clear.
EDIT: Toned down my phrasing in the article to be more specific about when you can safely remove X-UA-Compatible tags. Yes, there's an argument that it doesn't cost you anything to keep it in there, but there's also arguments for ultra-short head tags (<4 KB) related to TCP windows, which I'll get into in another post.
Also, I'm not familiar with the W3C process, but since this is a working draft, I'd assume they're invalid until the draft is finalized.
Scripts without an async attribute will cause the browser to stop where it's at in the DOM and wait for the external script to download. The browser will not start downloading any stylesheets that come after the script tag until that's done. This is all straight from Google and can be verified in Chrome Timeline. https://developers.google.com/speed/docs/insights/BlockingJS
> So if you put your CSS link before your JS link and the JS is not async, the running of the JS will be blocked on the load of the CSS.
Downloading CSS isn't required to fire DomContentLoaded, so most browsers will download it in a non-blocking fashion. Chrome does not behave in the way in which you describe, which is shown plainly in the article. Again, this can be verified in Chrome Timeline.
All that said, I'm curious as to what browser engine you work when where what you said is the case - I don't doubt it, but you're not describing the way Chrome (and, I suspect, Webkit) works.
Right-o on the bit about DomContentLoaded, will fix.
Even this has a tradeoff - if, for example, the other JS on your page require JQuery, you can't make the CDN copy of JQuery use an "async" tag, because you can't be certain of the order the JS will execute. And if you're not using the async tag, the first load will suffer.
HTTP2 will absolutely change a lot of how this works, you're right. I chose not to cover it as it won't be a real option for most developers until nginx supports it (still in alpha). The skills I'm teaching in the article re: the Timeline can still be applied when HTTP2 gains mass adoption, so you can test for yourself whether or not the recommendations in the article still make sense.
Combining all the resources will include assets that aren't needed. Part of the reason I made the post about profiling with Timeline was so that you could test tradeoffs like this for yourself.
I don't know what you mean by reducing the utility of CDNs and caching though - surely having only one file actually increases the use of browser caching, since the browser will only make 1 request for CSS and serve the cached copy for every other page?