Oct 21

I've slacked a lot on keeping this up. Various sources claim that it's important, psychologically, to journal what you do every day.

It's possible that where I am right now is a side-effect of the slacking. It's also possible that there's just a lot of frustrating shit going on right now. I want something that I can break. I'm frustrated with absolutely everything.

Google's shitty documentation for Android is annoying as fuck. The number of APIs that fail silently makes me want to strangle multiple people (I'm looking at you, Service interface, and you Intent, and you Alarms)

Lots of bugs and stupid problems. Progress is painfully slow.

I'm also fed up with the conceit that an Android application isn't really a program that starts or stops. Everything fucking stops. Assuming that your app is going to run forever and that you don't _need_ a way to tell when it stops it bullshit.

It turns out that there are (at least) two distinct types of Activities: the initial Activity that starts your application, and every other Activity. The difference is that the onDestory() is NEVER called on the initial Activity, but is reliably called on other Activitys. So ... hey guys, maybe this is a big indicator that you're trying to make the Activity class do a bunch of shit it shouldn't do. Honestly, if you have a method that is NEVER called, why is it there?

Seems like you should always have a shell Activity whose entire job is to start another Activity so that you then have a place to reliably handle onDestroy().

What a shitty day. I really despise days when everything seems like a gigantic chore.