bjxrn

The problem is that plastic recycling in general just doesn't work that well. If you want to make any sort of difference then reducing the amount of plastic you use & throw away is essential.

You can find some here: https://hashbase.io/

This was posted a few days ago: https://bof.nl/2017/02/14/kamer-kiest-voor-sleepnet-grootsch...

That's a modern addition.

http://netflixable.com/ has an overview for a set of countries. Maybe yours is among them.

I think you are thinking of "hominid".

I can't find it in the NYT article so maybe it was in the original paper, but I'm pretty sure the 7-minute workout was always meant to be repeated three times (although maybe not directly after another).

But even then you're left with compressed text. If you're concerned about the amount of data you're sending on the bit level, then you're throwin all that out the second you start pumping out JSON.

For me on Chrome, there seems to be some broken loop somewhere. It continually requests and then cancels those requests to certain sprite images. It still downloads at least part of them though, so you're getting maybe ~100kb/sec continually downloading for as long as you're on that site.

The distribution is a result of the low number of ratings. Look at the number of ratings for each episode. For all those early 7.3-7.4 episodes it's about 600 ratings, the higher rated episodes have more ratings. Then from about season 12 there's a drop in number of ratings to about 300-400 for most episodes.

Compare this to the Game of Thrones ratings[1], where each episode has about 3000 ratings.

[1] http://graphtv.kevinformatics.com/tt0944947

I haven't run into that limitation yet, but I've had a client site which suddenly had started looking broken in IE. It turned out that it had exceeded the 31 stylesheets/style tag limit. This was a site where the CMS theme/template set a few styles, but then was packed with extra widgets loading up to 10 styles each.

The solution was of course to simply join the CSS files where possible. But it definitely was a bit of a WTF moment.

There's also the "over" one which allows you to set a points threshold.

Example: https://news.ycombinator.com/over?points=50

1 meter = 3.28084 feet

1 square meter = 10.7639 square ft

Speaking of the cache and download sizes, when I reload the Google specimen the font files return a 304 (not modified) status while the Brick ones return a 200 code and have me download the files all over each time.

So for me it's 300k each time the page loads (Brick) vs 92k for the first page load and ~0 each time after that (Google).

Is this just me?

Why is it so hard to provide a nice sample sheet for fonts? Just a paragraph (or just a sentence for display fonts) in the various weights would be a huge step forward in most cases.

Just compare the samples of Hallo Sans (the first font in this list): https://www.behance.net/gallery/Hallo-Sans-Free-typeface/132...

To that of The Enschede Font Foundry's Trinité: http://www.teff.nl/fonts/trinite/pdf/trinite_a3_print-600.pd...

Well, "fuck" is okay too (for some people apparently). As in "Fuck you, pay me" http://www.youtube.com/watch?v=jVkLVRt6c1U (not by anyone from github, but still industry related).

Does taking advantage of the technology in the newer devices automatically mean you must have degradation in the older ones?

In that case, why not use latin1? Or hey, why not just ASCII?

The article's title is "Redesign: From PHP/MySQL to Node/MongoDB Stack". And isn't about going from PHP/MySQL to Node/MongoDB at all. Instead it's mostly about putting together a one page app sort of thing, rather than putting everything together server side.

I tried a Bing image search for Michelle Obama. The suggestions I get are: wedding dress, craig robinson, 2007, dess, swimsuit, fashion, eyeroll, pregnant. And I turned off safe search.

I suspect you enjoy it when other people are enjoying themselves, and that you don't get your enjoyment out of the manipulation itself.

"But is this even a real problem? No, not really."

If you have that luxury then that's great. For you. But if you're doing client work you likely don't have the luxury of never having to estimate. And even if you're not doing client work then it would likely be a good idea to at least give it a passing consideration.

Say you have a client who wants [x] and it needs to be done by a certain date (Yes! This does happen!), then it is helpful for you to know whether or not you might be able to deliver.

Say you have a client who wants [x] for [money]. Then it is helpful for you to know whether or not you might be able to produce it in a time frame which makes sense economically.

Say you have two ways of solving a certain problem. Then it is helpful for you to know if one solution would take a week and the other a year.

Estimation can be hard, sometimes impossible. But I'm not sure pretending it's not a problem is a viable solution for many.

That's largely due to taxes though.

I just want to point out that anyone can help the Archive Team by running an "Archive Team Warrior". It's a virtual machine which scrapes things that need to be archived. Currently Posterous, Formspring, various URL shorteners and of course upcoming.org (in testing).

It's really easy to set up and I would encourage anyone remotely interested to give it a try. More info & download: http://www.archiveteam.org/index.php?title=ArchiveTeam_Warri...

You want to know why people worry about older versions of IE? Because a large enough chunk of their visitors still use those browsers. It's that simple.

It's not just going over a blacklist though. If you do any form of checking/rejecting a password, you're probably infringing something. And it's not just the checking, the article also mentions "recovery of forgotten passwords, secure password resets, using one-time passwords, account lockout, generating pronounceable passwords, password hints, and even backdoor passwords".

Yes, to be fair, Gillette still manufactures and sells older versions. They even make & sell double edged razor blades.

But they definitely push for whatever is the newest (and usually more expensive) option.

There's no issue with the Mach3, or whatever came before it. They just want to push their consumers to the newest version.

Google Sidewiki?