erwanl

I've never heard a left-handed complaining about the traditional gamepad layout.

Well, that's the thing: if it was an obvious success from day one, others would have done it too.

On Google Play you can ask for a refund. The request gets forwarded to the developer who can accept to do the refund or not.

Steam could at least provide that.

They probably live in East Bay and have an awful commute every day.

Regarding #2, I've heard an interesting statistic recently.

The blue workers average salary went up 5% in one year in France. The reason? Recent waves of layoff impacted lower salaries more than the others. So the average went up, but the lucky ones who kept their job didn't see an increase on their paycheck.

Well, the thing is both Chrome and Firefox get updated automatically but IE doesn't.

So the problem will not IE versions that are already old (IE6, IE7) but current versions of IE - even future versions before they implement these new standards.

As these features roll out to Firefox and Chrome, users of these browsers will have to them because of the auto-update pretty quickly.

Eventually IE will implement them, maybe in version 12, and you'll have users still using IE10. Heck, maybe they won't be able to upgrade their IE because it won't run on their aging Windows 7.

Unless IE switches to the auto-update used by Firefox and Chrome, and stops dropping Windows versions in their new IE, I don't see the problem going away.

It's not that it's "Scala adapted to Java", but more like a choice to do async and functional programming even in Java. That makes stuff a bit verbose sometimes because to pass a function you have to pass an anonymous class.

That will become better with Java 8 and lambdas without having to break compatibility with older Java versions (they will still use anonymous classes).

I actually remember hearing an official from Cote d'Ivoire insisting that we should use "Cote d'Ivoire" in all languages.

People localizing their country name creates confusion, typically a citizen from Cote d'Ivoire unable to explain to an airport official where he's from because the official only knows the locally translated name.

Unfortunately modularity goes against the interests of companies producing gadgets. They'd rather have you buy a full upgrade every 2 years than just change a few components once in a while.

Yay, SOAP in JSON!

It's actually what's happening on mobile. Everyone uses webkit but they all have a different version, with their own set of patches and compilation options.

So it's as fragmented as on the desktop.

The user is not necessarily the customer, or the buyer.

In a company, the buyer or customer may be a manager but the user the members of his team.

In a consumer product, the buyer or customer may be a middle-aged man but the user his 12 years old daughter.

Words have meanings, and randomly inverting them will only cause more confusion. When you sell a product it's important to know who is the custmomer and who is the user. If they're not the same person they will have different goals and needs, and it is important to understand them.

cdnjs has been around for a while already.

You can certainly drop an iPhone without breaking it - but I wouldn't be sure it would work every time.

Also, scratch-resistant and drop-resistant are not the same thing.

Or, buy a phone that can resist a 1 meter drop on concrete without a case. That's pretty much any phone except the iPhone 4 and 4S. http://www.youtube.com/watch?v=elKxgsrJFhw

Yes, sure, full glass is beautiful. But not very drop resistant.

Even if that's the case, they did not sat in a room for 2 years waiting for the iPhone release, then suddenly shouted "let's clone this thing!"

(Yes, I know that's what Steve Jobs believed.)

No, not search engines. Merchant sites like Amazon on the other hand let you get affiliate money without having to bind a special deal.

That would be true for Amoled screens, but for now they're only used in mobile phones.

Who cares about Instapaper for Android? ReadItLater is at 10c on the market right now.

Leave short-minded developers to their Objective-C and use apps from developers who care about the platform you chose.

We're still in line with our "no useless boilerplate" approach in Play 2.0. You can look at the samples and make up your own mind about whether we've been successful or not:

https://github.com/playframework/Play20/tree/master/samples

I agree with him - what Guava brings (functional programming, better safety in types) is something that is better done at language level like in Scala.

Either you like Java and you don't need Guava, or you want functional programming and other goodness and for that Scala is a better language.

Battery life is pretty good with Gingerbread.

ICS will be able to run on any phone able to run Gingerbread.

The idea is to build voice recognition from a large base of samples from different people (male/female, age, accents...).

That's why Google offered GOOG-411, mostly to train their database. And that's why all these solutions include a server-side part, because they need the large sample database that keeps growing.

Well, the things is that if you include resident medecine studies are really long. So: * You'd have to average for a life time of work * You need to make sure you subtract the cost of studies (although in US pretty much any study costs a ridiculous amount of money) * You may also want to take into account that you start making a good salary late in your life, at a time you'd need some (like when you want to buy your first house)

Anyway, I don't know about US but in France doctors are not that bad. They have pretty competitive studies and they also have a few resident years, but they don't have to pay for study (as for any student) and pretty soon they get their well paid job. They also don't have as many stupid trials as in US.

It does scale, believe me. In order to scale you have to be able to load balance to accommodate a higher load.

Using exceptions for flow management doesn't prevent you from adding more boxes. If you're thinking it can cause performances problems, I have an app in prod; here are some numbers: * With a single box, we can do about 500 req/s for a dynamic page, accessing the database * It appears that the bottleneck is the template engine. If we cache the result (thus serving a "pseudo static" page) the exceptions-based control flow is still there but we serve up to 1000 req/s. (That's more than Apache can do to serve static content on the same machine).

So yes, Play does scale!