Having a standalone GCC installer is a nice option (especially if you have an Air with limited disk space), but if you want to avoid the hassle of debugging the occasional compilation failure, Xcode is the way to go.
Turntable's design sense was its differentiator, and many of my friends were completely charmed by the avatars when they first tried the service.
If you actually do want the functionality of Turntable without the avatars, http://listeningroom.net/ came out awhile before Turntable, but never seemed to pick up.
While the same thoughts crossed my mind, I think he probably meant art in the age of mechanical reproduction.
Still, programming affords a combination of the widest reach and lowest barrier to entry: it rarely requires the artist, performer(s), or specific location(s) to be consumed as a medium.
I agree with what he meant, but I dislike his use of the word "only." I hate to be really anal, but that kind of thing always sticks out in writing to me.
"Hard distinctions make bad philosophy." as John McCarthy (of Lisp and AI fame) would say.
A friend and I built http://failin.gs with the mindset of vanilla anonymous feedback but were surprised when a lot of people started using their profile as a forum for feedback on their artwork and other hobbies.
These kinds of resets often seem like overkill. Are there any reset libraries out there that do the bare minimum by normalizing against user agent defaults?
> Are there any reset libraries out there that do the bare minimum by normalizing against user agent defaults?
Looking at that chart, and looking at Meyer's reset, I'd imagine that your suggestion would lead to a much larger CSS file. As it is, reset2 is fairly short.
I don't mean in bytes, I mean in how many elements it applies rules to (see rimantas' comment). I'm also not sure it _would_ lead to a much larger CSS file (only 16 tags differ among browsers, and I doubt 16 CSS rules would be required for normalization).
Gotcha. But still, the chart is old, and lacks browsers people use. The benefit of the CSS reset is that it resets everything in browsers so everything is equal. Normalization wouldn't exactly do that. And if things changed, the normalization would have to change as well.
Good idea, but practically speaking, I think it defeats the purpose.
Perhaps, but both the Mozilla and WebKit stylesheets are available for reference in their respective repositories (and likely unchanged, for the most part), and IE9's purported stylesheet is here: http://www.iecss.com/
It would be doable to keep up to date if someone wanted to, though whether it's worth the effort is another thing entirely.
I'd also like to hear some pragmatic CSS professionals weigh in on this topic. From what I've seen so far, I agree that some of the resets are over the top, but I'm not sure whether the opposition to them is a result of purism over pragmatism. I really just want to speed up CSS development...
> I really just want to speed up CSS development...
Meyer's reset is not supposed to speed up development. On top of ensuring basic consistency, Mayer's goal is (was?) to avoid taking default styles for granted, think more about document and re-create all those styles for it:
If you just want consistency, but don't want to spend extra time re-creating basic defaults, then unbolding of strong, unitalicizing of em and few other such resets don't make sense.
I'm finding that they are less relevant than they used to be. We are beginning to have more consistency across browsers, fortunately. I've been working on projects lately that don't employ them with very minimal issues.
Never use them, never will. I just don't see any benefits and I hate how reset stylesheets pollutes firebug or webinspector CSS panels with inheritance nightmare.
I was interested but as you note registration is required and one doesn't even get an explanation or a screenshot without signing up.
Also, supermarkets move all their stuff around every few months in order purposefully to disorientate shoppers. I'm surprised that any want to sign up and would be inclined to think that the data is likely to be wrong quite a lot.
We update AisleFinder on a 4 Month Cycle by verifying product/aisle info. We have done analysis/focus tests to find that we have a 97 % accuracy in our info as well. The only reason for that 3% is items like Honey (which can live in many different places in a store) unlike some people we dont speak before we know something for sure.Thanks for your feedback though. I will let HN know when those numbers change.
