Out of interest, what breaking changes have been introduced to C in C99 and C11 (I’m assuming we’re using C89 as a baseline) beyond changes in corner cases in tokenization due to the introduction of “//” comments (and perhaps the removal of gets)?
I don’t understand figure 5. The left and right images are not only of code that’s not highlighted and that’s highlighted, it’s for two completely different functions. Of course eye tracking is going to be different.
Even though it’s not really worth noting due to the first issue, the right example also seems to require more focuses (87 over 65)?
It was worse than that. Someone wasn’t worried. Instead of acting, by, say, trying to talk to the kid in the car or perhaps just calling the cops, they “recorded the incident using a phone’s camera, and had then contacted the police”. Baffling.
I agree. Sadly, similar services don’t generate results even approaching those of Google Code Search. The interface was also a lot better than that of its competitors. That’s not to say that it couldn’t be improved, but if there wasn’t time or resources for that, then they could at least have left it running.
One of the best resources for ”programming by example“ is now gone and the world is worse of for it.
I believe that this quote says a lot about what supporters of SOPA believe:
> The purpose of this legislation is to target foreign sites that are stealing U.S. property.
Classic “us versus them” rhetoric. There are foreign groups out there working against us (or is that U.S.?) that need to be stopped. We may end up running over some of our own along the way, but it’s all for the greater good. Remember, there are people out there that want to harm you. Wouldn’t you rather be harmed a little bit by “us” than maybe a bit more by “them”?
Ah, here’s that “I eschew embedded capital letters in names; to my prose-oriented eyes, they are too awkward to read comfortably. They jangle like bad typography.” comment I’ve been looking for. It seems he changed – or someone forced him to change – his mind on this in Go.
I tend to agree with the idea that Google Circles is broken. The problem is that one also needs the reverse. I, as a content producer, need to be able to specify to those that I’m sharing with what it is that I’m sharing with them. This way, content consumers can choose to follow the items in my stream belonging to a certain category (or circle or whatever you want to call it).
As an example, I would like to be able to follow Ryan Dahl and get content from his stream regarding Node.js. I don’t however, need to read about him standing in front of some skulls: https://plus.google.com/115094562986465477143/posts/CEMdcTeE.... Currently, there’s almost zero information in his stream that I care about, but the only way for me to get to that information is to let all of it pass through my stream.
OK, so everyone agrees that it’s less discoverable, but how many actually used the old bar? I have only clicked an item in that bar once. When I realized that it opened a new tab I never clicked any of the items again.
I’m not clear on how this new selection will work, but if it lets me switch between GMail and Google Reader from one menu and remain in one browser tab, I’m happy, even if a bar would have been a little quicker for switching.
First of all, you should be measuring in points, not pixels. Secondly of all, why set font-size at all? Leave it at what the user has set it to and adapt your layout around the possibility of a range of font-size values.