The link was originally from http://www.underconsideration.com/brandnew/archives/youre_not_wrong_youre_just_an_asshole.php.

I see this a disheartening amount, even on DN. People saying "this sucks" or "meh" about someone else's hard work, when it might have been more constructive to talk more precisely about why something doesn't work.

I know complaining about Internet comments is like complaining about the tide, but it's still worth thinking about.

There's this site:

https://randomuser.me/

I agree. The "What if there weren't more episodes" angle is really pitchy. I think public radio's pitches have a lighter touch.

I'm not really bothered by the "we need this money" angle they went with. (I might be biased -- I heard the plea on the podcast first, and ended up donating without really reading the site's pitch.) But I do agree that the best pitches involve selling the product, not selling the circumstances.

My angle, if I were writing this pitch, would be focused on "we're going to make a season 2, and if we have your support, this is how great it'll be." Focus on the positiveness of the upside.

I never use Siri because you have to press a button to activate voice control. If I have to get my phone out to press a button, why don't I just unlock my phone and find out what I want to find out?

This object doesn't require a physical action to activate voice commands. When you need to do something, it just works. Privacy implications aside, it's a lot more usable than Siri.

It's a huge dealbreaker that Firefox doesn't support image masks. Which is a bummer: they're very useful, and they're used in such a way that they don't gracefully degrade when not supported.

That's like saying "why go out to eat, just Google a recipe and you can cook pretty much everything they offer in about 2-3 hours." Taking the backend server maintenance out of the equation (not to mention the detective work on figuring out how to integrate all those third parties) could be a huge timesaver for a lot of frontend devs.

The product looks pretty polished, and I could see the value in using it to quickly bootstrap a project with a simple REST API and OAuth authentication. There are some things I would personally like out of the product -- like some text labels, since it's easy to get lost -- but it seems workable. And Stamplay is entitled to charge a price for what they offer.

I'm guessing that the advantage of the mixins is to make the role of each ruleset 100% clear and unambiguous. Standards are easier to enforce the more clear it is when you're following them.

It's also arguably more readable to see the mixin declaration than the -- and __ and + around the file, in addition to your standard --'s and .'s and #'s.

It would also have the side effect of reducing the number of errors you get from typing one underscore instead of two.

I think you're losing the forest for the trees. The new design is clearly better than the old one. It's not going to make Yahoo into the most popular site on the Internet, but what is?

Nice! One minor suggestion: right now, the click area on the top navigation is tiny. You have to be directly over the letters to activate the click area. If you add padding to the anchor tag and reduce it from surrounding areas, it'll be a lot easier for people to click!