Is this really true? I'm interested in hearing the opinion of an engineer from one of the browser teams. Who's to say that any device can't have a precomputed value for the pixel-to-centimeter ratio? It should be easy and quick to compute. Perhaps it would be even faster for a browser to render it than more fluid elements.

But I think that being able to perform media queries on screen sizes would be extremely useful. I just sat through Luke Wrobleski's talk in the first day of UI17 conference, discussing that instead of discrete classes of screen sizes, there's really a continuum of screens, all the way from 3 inches to 30 inches wide. So... where to set your breakpoints? You can't depend on screen resolution, since some smartphones have more pixels and a higher resolution than most desktops. Being able to measure the real screen width as well as pixel width in a media query would be a real help in setting breakpoints.

Ping Identity is an excellent, fun company to work for, and our headcount and business is in huge growth right now. Please take a look and submit your resume if you're interested.

I started getting curious as to how it worked. How did the sender get an image into what's usually a text field? Or, was Gmail adding it as a UI element to identify travel-oriented emails?

Taking a look at the email source, I noticed the following code in the header:

From: "TripAdvisor"
To: <######@##########.###>
Subject: =?UTF-8?B?4pyIIEJvc3RvbiBhaXJmYXJlIGRlYWxzIC0gd2hpbGUgdGhleSBsYXN0IQ==?=
Date: Fri, 05 Oct 2012 11:12:46 -0600

What that subject header encoding means is that the subject has been base-64-encoded, like this:

=?UTF-8?B?#Base64Encode('✈ Boston airfare deals - while they last')#?=

Cool stuff, and very creative on the part of the senders. Now I just hope that there aren't many UTF-8 compatible glyphs out there. I don't want my inbox to get so crowded with them that they lose their utility.

The issue is with the use of both the media declaration and the web fonts. Which media values cause a problem? Looks like all of them (all, screen, print, etc.). Remove the media declaration and your web pages will then show the fonts your designer specified:

@media all { /* Remove this media declaration and start brace */
     @font-face { 
          font-family:"Frutiger";
          src:url("/fonts/frutiger.eot?iefix") format("eot");
     }
     @font-face {
          font-family:"Frutiger";
          src:url("/fonts/frutiger.eot?iefix");
          src:url("/fonts/frutiger.woff") format("woff"),
               url("/fonts/frutiger.ttf") format("truetype"),
               url("/fonts/frutiger.svg#frutiger") format("svg");
     }
} /* Remove this end brace */

If you need to keep your media declaration in your stylesheet, then I suggest that you just move all of your font-face calls to a new stylesheet.

1. Every meeting should have a clearly defined mission statement.
   Absolutely correct, every meeting should have a clearly defined set of goals, and they should be clearly stated, both in the invitation and at the start of the meeting itself.
2. Do your homework before the meeting.
   Not only will you look good if you're prepared for the meeting, but you'll be helping everyone else be more productive.
3. Summarize to-dos at the end of the meeting.
   This is as important as stating the goals. Someone should verbally summarize the action items and conclusions from the discussion.

1. No meeting should ever be more than an hour.
   I certainly agree that the shorter a meeting is, the better. But some meetings, especially brainstorming meetings or project reviews, are going to take longer than an hour. There's no reason to set an arbitrary duration that's called "too long".
2. Make it optional.
   I don't see how it's practical to make every attendee optional. People should still feel free to decline an invitation, but sometimes you need to make it clear just who you can't have a meeting without.