236 karma · joined May 14, 2010
No need for the negativity, can't blame those guys for wanting to get a larger userbase by making things easy. In the end the larger volume/bigger community is beneficial to everyone.
Edit: My source is a knowledgeable person on the subject, feel free to contradict or doubt the truthfulness of the answer - makes sense to me at least.
- What if you get a negative result (i.e. you're ok)? Are you just gonna live happily ever after, ignoring any symptoms of sleep deprivation since you have already ruled out apnea?
- What if you get a positive result? You'll still have to go through the same kind of studies again, no doctor would give you much credit for your home study.
So, if you suspect you have sleep apnea you should go talk to your doctor. Your notes on sleep apnea are good though... it's a serious and a very commonly undiagnosed/untreated condition... even thought the cure is in most cases relatively noninvasive and cheap(CPAP). People above average weight should be particularly alert to typical symptoms (sleepyness, lack of energy).
I'm not sure why java uses .length for arrays and .size() for collections ... but could it be that it was for similar reasons?
Requests is great by the way, had already written some code to abstract away the urllib/urllib2 mess but this module is so much more complete (of course) and cleaner.
Btw.: On phones that have hardware buttons (but no dedicated search button, like the European version of SGS2) you can open search by long pressing the menu button on the home screen.
public class C { public int foo() { return 1; int b = 1 + 2; } }
Then compile it (javac C.java). You will get the following:
C.java:4: unreachable statement int b = 1 + 2; ^ C.java:5: missing return statement } ^ 2 errors
Therefore this code is not compileable, thus telling us that the initial code blob could never have run in the first place.
I'm not sure why the decompiler returns non-compiling java code, I just know it does.
I'm not saying that the conclusion of the article is wrong, I'm merely trying to explain why the code blob above looks so weird.
Be humble if people are willing to pay you more money than others for what you do - it might change incredibly fast. The more generic assumption of the post is that people are willing to pay good money for skills that are relatively rare... well, make sure to keep your skill set up to date.
So I installed cyanogenmod 9.1 and I fell in love with my phone again. It's not perfect though but I don't think I'll ever want to buy a non-stock Android phone again...
So being a rather passionate Android guy I do recognize that there are very annoying problems with some Android devices. And installing cyanogenmod is way above the skill level of the average phone user (even though it's rather easy).
Sometimes I wonder if iPhone people experience the same kind of disappointments ... and when they do it makes me feel a little warm inside. I know it's not nice but I guess we all need to justify our own purchasing decisions to ourselves every now and then :)
The point here is that you have to create a new layout for the iPhone 5 (if you don't want your app letterboxed) and this adds an extra layer of complexity to the development. Seeing that there are also rumors about a different form factor iPad you would then have to maintain 6 different layouts (standard/retina/16:9 for iPhone, standard/retina/new layout iPad). Well or 12 if you have specific landscape layouts.
Designing UI on Android apps can be a pain since you don't have the "pixel perfect" paradigm, which is a common criticism on Android from iPhone developers, but if you manage to get them right you can get away with a single xml layout (of course, you can able to make things more complicated).
It seems to me that Apple are getting themselves in a bit of a mess with this. The tradeoffs with the "pixel perfect" method haven't really materialized until now.
Maybe I'm just being over pessimistic with this and it will be a non-issue, I really can't tell at this point, but I see this as the greatest issue with the iPhone 5 (which in turn is probably the reason they didn't increase the screen size earlier).
Of course the "web app is sufficient" point is irrelevant though, it's fundamentally weird that someone is making arbitrary decisions on which apps are allowed and which ones are not.
It provides support for features from Android 3.0 (namely fragments) for all versions down to 1.6. IMO it's essential for Android development.
EDIT: Of course you have to make sure you don't do any writes that block the main operation, e.g. by using message queues.
However the iPhone UI is much more polished. That can hardly be debated, feels to me like the Android dev team "just made it work" and didn't have too much time to worry about polish.
I really hope ICS fixes that.