Reading the title I immediately thought these set of articles on procedural city generation. It's about the visual appearance of a city but very interesting nonetheless.
From a developer's standpoint it does matter. Every OS version, hardware version is another platform you have to support and test against. Even on identical hardware with an incremental version difference it is not uncommon for some strange edge case to cause something to break.
Simply not true - as long as you don't use internal APIs, apps made for an older Android are completely compatible in newer ones, and new APIs are usually backported to older Android versions with compatibility libraries. When you update your Android OS, all of your apps will continue to work the same and you don't even notice.
Contrast this to iOS - whenever there is a new iOS version, developers have to scramble to update their apps because they very often break or the UI is broken by changes, etc.
Android is much much less hassle when OS updates roll around, and I develop for both.
I back RyanZAG here (hey Ryan :) ). I went from 4.1.2 to 4.2, 4.3 and now 4.4.2 without hassles. The exception is KitKat where a lot of developers updated their apps specifically to support the new ART.
[Rant]: I find that it gets a bit silly in iOS land, in the sense that local (South African) devs who have abandoned/flopped apps had to go and update their apps after forever to match the 'look and feel' of the new iOS, whereas with Android one can go without noticing that.
As someone who has done a fair bit of Android development, it's ironic that you mention that. The Android design guidelines tend to change on six month basis, and not always for the better. Sure, the changes are usually smaller, but it can get pretty annoying after a while.
Good point. Of course another interesting way to look at it might be to see if there are multiple maxima. Perhaps if he advertised a very high rate comparatively to the competition, he could find another stable price point. Or perhaps he might just be able to keep going, pushing the limit of what people will pay, while keeping up the high quality work. Bit of an Apple strategy! It does help if the product/service is very good of course.
How robust is the mobile detection? If using the user agent to determine a mobile browser results in many false negatives then not directing from the mobile site version is a good idea.
Edit: To be more clear. If you are on a mobile device and you are trying to access the mobile site but the server can't reliable determine that you are in fact on a mobile device it would be bad to auto-redirect. At the same time accessing the mobile site on desktop browser should still allow the site to be usable.
The issue with linux containers is (or at least it used to be) that it is possible for a malicious user to 'break out' of the container. Has this problem been solved?
This is good news if you want to be able to purchase movies on the cheap. When a Blockbuster closing a few years ago where I lived they sold off all their movies. I think it got down to $2 per Blu-ray movie by the end and I picked up more than I care to say.
TypeScript was obviously on your mind. The readme states 'Functions in TypeScript can have zero or more arguments in general, just like in Javascript.' You might want to change that to 'PureScript'
http://www.shamusyoung.com/twentysidedtale/?p=2940