psquid

That's the point. You can't change the format strings to a different word order if the selection of values used to fill the fields is entirely dependent on word order (i.e., how the basic printf syntax works), unless you have a separate line/block of code that executes when the word order of the current locale differs.

Is it just me, or do the ghosts seem to all be moving fairly randomly, rather than following 4 different, but consistent, behaviours (like in the original Pacman)?

Whoa, I hadn't caught the Shadowrun one. Looks like that's another $30 I won't have any more - good thing I feel it's worth that. :)

A good read, but a little disappointing that it didn't touch on the (function(...) {...}).bind(this) approach to passing the parent "this" context down the function tree, preferring instead to use an extra variable in the form of "_this".

Nope. Android apps are, with one caveat, independent of any particular architecture, due to their Java/Dalvik base.

The only situation where anything developed on x86 would not also work on ARM is if you include native code via the NDK (which is not usually done except where you need to wring every last bit of performance out of the device), and that's just a matter of building the native code for all the platforms you intend the app to run on.

The platform used by the emulator image makes no difference to any of that, it just makes it a lot more practical to get usable speed out of it.

I wouldn't be surprised if an impromptu communication protocol (based on assigning meanings to things other ships can observe you doing) sprung up pretty quickly to allow networking. At the point that ships can communicate, it's bound to come down to needing to do it with securely-written code, or risk ship-to-ship malware.

Should be really fun to see where this goes.

Agreed, though I'd say posts like this one are something of an exception; if you weren't already aware of the story, you wouldn't even think to search for it. So it serves as a sort of "hey, HN users, you might be interested in this" post, rather than a discussion area for an article which people might well find via other sources, and want to see discussions about.

This is specifically a flaw in the libVTE terminal library, which OS X's Terminal.app is not, to the best of my knowledge, based on.

Yeah, it seems to me that committing a fix with a commit message along the lines of "Oops, you left this open. Don't worry, though, I fixed it." would've been the best option.

> I wonder how if those private tweets are included in the bundle.

http://www.bbc.co.uk/news/technology-17178022

"private accounts and tweets that have been deleted will not be indexed by the site"

Any idea where someone (such as me) born too late to have an original Micro might be able to get hold of one?

> Within the next year Google will have you go full screen in GTK inside Chrome/Debian ... then that's your desktop

Source? Or is that just conjecture?

Gah, why would they use a bar chart for the "Getting Into Github" diagram and then not stick to anything resembling a consistent x-axis - at first it looked like it might be exponential, but it's not even that. The bar sizes are nearly meaningless, because different segments of them are to wildly different scales. All it actually conveys is "this one is more than this one".

The important difference here is that your examples involve something physical; in both, he has eaten some food that can thus no longer be given to anyone else. Whereas, if he downloads a copy of an eBook, the publisher can still sell copies to just as many people; he has not removed any finite resource from the system.

I'm still not sure it's justifiable (though I'm leaning slightly towards it being so), but it certainly isn't comparable to what you're saying it is.

Seems to me that the advice in the OP is intended primarily for someone doing a startup (or planning to). In that circumstance, you're probably not going to stick with such a high risk, even for high potential reward, unless you yourself fit into the group that would use it.

That is to say, you yourself are the client (sort of), meaning there's not so much need to make any effort understand the client, because you already know what you know/how you feel about $THING(/etc.).