True enough. But reading that article, it seems that it's mostly a branding issue. And they may be concerned about upsetting people who have come to identify Android with Google services.

I haven't really looked into it but I believe it runs standard Android apps. Of course, without the Google services, a lot of apps won't run but that's more Google attempting vendor lock-in in my opinion.

I haven't looked into the Amazon app store so I don't know how good or bad it is. I do know that as an Android dev, I fairly regularly get contacted by people claiming to represent other app stores who offer to include my apps (or do it without asking) but I have heard nothing from Amazon so far (though I'm thinking I might try putting my apps up there anyway).

The Amazon Fire Phone is Android based but does not use Google services.

I don't know. I think it's case dependent. In the example cited, the cleanup code is simple function calls and the operations are different for each case (for one, it's one cleanup, for another, it's two and for the success it's three).

Part of the problem is, the examples are really too small to call either way. I try to aim for my code to be clean and understandable and not to be dogmatic about things. I avoid certain Perl idioms for just this reason. Though I certainly agree that TMTOWTDI

Yeah. I don't see it being abused too much. I avoid using it but I wouldn't have a huge problem if I saw it and it wasn't being abused terribly.

True enough. And it may well be the solution to a real problem that isn't recognized or possibly even invented yet. I don't think using light fixtures as data communication channels is likely to be it though.

This is the summary I was looking for. Good work.

Those operators are merely symbols that represent a subset of things they can do in the "real world". Why not allow them to represent a bigger subset of those things that they can do in the real world?

Good point.

The difference is that it's immediately obvious what a return statement is doing whereas the goto puts the flow of code "elsewhere" and might be leaving things in a weird state (granted that the OP has since claimed he intended to put some cleanup code before his return which could change the circumstances).

Not even just for error conditions. I think something like "if(x==NULL)return EMPTYSTRING;" at the beginning of a function for special case handling is very readable.

OK. So now why is white better than blue? Or, indeed, the IR that was once fairly common in phones in the late 90s?

Oh, I see. They want to use the room lighting to do this? Seems like a solution looking for a problem to me.

XP had more demanding specs which was adopted pushed the netbooks out of their value point (they failed to be competitive with low-end laptops).

Tablets vs netbooks is yet to be decided. Tablet sales are flattening and Chromebooks are still out there.

Did that chafe when you pulled it out of your arse?

I don't believe he said that Windows 7 killed the notebook, merely that Microsoft's efforts to take a slice of the pie were damaging to the market