JoelSutherland

Apple stock has been up 4/7 times the day after the announcement of an iPhone.

The Uber for Everything is called Craigslist.

It's a fairly efficient market which means you can generally buy a used drill for the same price that you can sell it for.

You're using chrome on windows right? The linked URL is their mobile site and the text container has been 3dtransformed forcing grayscale antialiasing which Chrome does poorly.

Check it out on Firefox or IE and you'll see what I mean.

It will look much better on a mobile device as well. If you drop "mobile." from the url you'll get their normal desktop site which also has much better type in Windows Chrome.

If it weren't for submissions like these, how could young developers that visit HN learn how to make ugly comments?

I'm with you up until the corporations ask for a repatriation tax holiday for the cash in the havens.

This may or may not be good advice but it has nothing to do with the article.

I don't think you read the article.

"Schools should recognize the legitimacy of AAVE as a language for their students, and teach those students to recognize when and how to switch between AAVE and American English as appropriate. But most schools don’t do that. They simply teach students that the way they speak is wrong. Don’t talk this way; talk our way.

Wheeler says we’re still not doing right by children who grow up with AAVE. “The consequences are that students are being terribly misassessed in our schools. Teachers think that black kids are making mistakes, when really they’re re-creating what they hear and learn at home,” Wheeler says. “They’re counting as mistakes things that are patterns and rule-based, so [the students are] being placed in lower reading groups.”"

The point of recognizing AAVE is not to teach it as a replacement language. It's to treat it similarly to Spanish for example. By recognizing where kids are coming from, the system will better be able to direct them to where they need to be.

J. Kenji Lopez-Alt is easily my favorite food blogger. I read just about everything he writes because he ALWAYS puts in this level of effort and detail. Towards the bottom of this page is his list of posts:

http://www.seriouseats.com/user/profile/GoodEaterKenji

If you found this post fascinating, there are plenty more like it.

It sounds like there probably wouldn't be enough data to generate the ghost players. According to the article they depend on the skills of the individual covers. (i.e. Player X is a 35% three point shooter so don't leave him in the corner to help on a cut)

The 82-game NBA schedule really helps to generate large enough sample sizes about players.

I could see it being potentially possible to just use average data, but if your rec league is anything like mine, talent ranges from a guy can credibly fake a three and then dunk after one dribble to guys that can barely get up and down the court.

It was written two months ago about chips that are still the newest on the market!

Isn't it pretty obvious what happened?

Microsoft built an OS for hybrid devices. ARM chips can't run legacy apps so Windows RT is DOA. Intel didn't have low-power, high performance chips ready for launch. So there are no good Windows 8 devices out yet.

We'll know a lot more about Windows 8 in a few months as some non-crippled hybrids are released. It's hard to judge Windows 8 on bad hardware. Microsoft should have held off on the release.

It will be less than 40 points wide, but the physical size of that button is still big enough. It is the exact same size as buttons on the iPhone.

You're saying that buttons on the iPad mini must be physically larger than buttons on the iPhone? For what reason?

You're missing the point entirely.

If you're concerned about the size of touch targets on the iPad mini, they are already the EXACT same size as the touch targets on an iPhone since the two share the same pixel density and recommended touch target size (40px).

    iPhone 3GS: 160dpi
    iPad Mini: 163dpi
    iPad 2: 129dpi

The iOS guidelines are 40 points for a button on all devices. So a button on an iPad mini is the same physical size as a button on an iPhone. Complaints about fixed finger sizes don't really make sense to me. If buttons on the iPad mini are too small, so are the buttons on every iPhone app made since 2007.

Regardless of how you meant it, it is a cheap jab. You speculated without proof that Atwood engaged in immoral behavior. That is a pretty bad thing to do.

Amazon's table is pretty shoddy, but being misleading in the other direction doesn't right the situation. There is more incorrect information in your comment than in their table.

Some key points:

1. Amazon has only ever used LCD screens on the Kindle Fire product line. They have always used notably excellent displays: http://www.anandtech.com/show/5128/amazon-kindle-fire-review

2. You're right, calling 1024x768 "standard definition" is a lie.

3. Amazon's is larger in both dimensions and is not 720p. (1280x800 vs 1024x768).

4. MIMO WiFi is a real thing. It might not be a huge deal (primarily increases max throughput, which is rarely a constraining factor), but the table is correct.

None of this is to say that the Kindle Fire HD is better than the iPad mini, I'm almost certain it is worse. It's just that facts are facts.

According to Amazon, 1024x768 is standard definition when in a tablet, but high definition when in a TV. Plasmas that are 720p are almost universally 1024x768 natively.

Additionally the A5x was a really expensive chip to produce. It didn't have the graphics power to drive the retina screen so they just threw silicon at it. It had twice the die size as the Tegra 3:

http://www.anandtech.com/show/5685/apple-a5x-die-size-measur...

The "newest" Core 2 Quad is nearly 5 years old. A quick google search reveals that computer uses a Q6600 which is nearly 6 years old:

http://www.techspot.com/review/36-intel-core2-quad-q6600/pag...

That's a pretty irresponsible omission by the author. It's about as bad as his claim that ChromeOS is based on "Ubuntu Linux".

Chromebooks just run a browser. Windows runs a browser and other things. Even if there aren't that many other things, your comment is fundamentally wrong.

They could have released this with an Atom processor at the same price. Windows RT is such a huge gamble for Microsoft. It will either sell enough copies to push developers to Metro or turn a lot of people off to Windows 8 before the "Pro" tablets even come out.

This isn't something to count on yet when it comes to ranking well. That article says "don't expect to hide something behind JS".

The good news is that individual post pages using the OP's blog engine have content in the HTML and appear to rank just fine. The value of a well-ranking homepage on a personal blog is probably overrated as individual posts tend to attract links instead.

Additionally, Chrome 22 changed the behavior of -webkit-font-smoothing: antialiased so that the weight of fonts looks much different than it used to when this was enabled. It makes icon fonts look especially bad.

http://code.google.com/p/chromium/issues/detail?id=152304

If this is true, I would wager it has the same specs as the current Nexus 7. The Tegra 3 that is currently used is printed on an out-dated 40nm process:

http://en.wikipedia.org/wiki/Tegra#Tegra_3

Printing the same chip on say a 32nm or 28nm process (Like the iPad 2,4) would dramatically reduce the cost.

This would also allow them to use a smaller battery and achieve the same battery life.

The major challenge is the LCD panel. It's plausible they could continue to use the same IPS screen, but using a nice TN screen is another place they could cut costs. They could also just wager that these are going to sell like crazy and work out a deal at volume like Apple does.

Because the image is reused in the CSS, it gzips very well. The 75kb CSS file gzips to 7.3kb!

But don't completely disparage it. It saves an HTTP request to include it in the CSS. (Though typically it compresses 30% worse. For smaller images like this, that is not an issue.)

Wait, if screwing over developers doesn't affect 99% of users, what is the point of doing it in the first place. To capture 1% more revenue?

I suspect in reality they expect their change to ultimately affect more than 1% of the user base.

At this point I don't think people expect anything from Twitter. They may not have fully burnt the developer bridge but they are close.

The way forward they chose, building another walled garden, was not the only way forward. It is the least creative and screws over the people that made them successful in the first place.

Here is a video comparing the 3gs to the 4s for internet browsing speed. The complicated sites are much different the simple sites are basically the same:

http://www.youtube.com/watch?v=HuSYkdyfuTA

I expected it to be more of a blowout on ALL sites. I can't tell if this proves you right or wrong.

Raw speed per core is increasing DRAMATICALLY in mobile. Faster than even Moore's law would dictate. As the die process has shrunk, more transistors are fitting within the mobile TDP ceiling so modern processor methods are finally getting used. As recently as the ARM A8, out-of-order execution wasn't even used!

You can verify that this is correct by looking at any benchmark.

Intel Medfield idles at 2.6 Watts and peaks at 3.7 Watts. The Windows 8 tablets will be using its successor, Clover Trail. there are roughly 40 tablets that will launch with it.

Intel isn't efficient enough for phones (see the comment below about the 1W tdp ARM SoCs) but they are efficient enough for tablets. Every report indicates they are price competitive as well.

Additionally, Clover Trail is being printed at 32nm vs. Krait's 28nm. It was just announced that Intel is going to bump up their timeline and move their Atom SoCs to 22nm next year.

It's not like Intel is destroying ARM by any means. They are barely keeping up. But that's HUGE on Windows where you have decades of legacy x86 apps that you might want to run.