17
MM83
2y

I think, after a few weeks, I'm actually quite enjoying that the Android SDK is genuinely awful.

We all know the feeling: "This is shit, whoever designed this is a fuc...oh, I get it. This is pretty cool actually."

So, it's nice to encounter a genuine dumpster fire of a platform.

I think the beautiful thing about its absolute obsession with providing a context to every single operation, is that you end up passing it around so much that the very concept of context becomes redundant.

Honestly, half of the stuff in here I've just attached to a global statics class, because it saves having to request a context, or a manager or some fucking kind of adapter, and it works just fine.

I've started to laugh when I look up a solution and see the browser scrollbar shrink into infinity, because the recommended answer is about two whole pages' worth of boilerplate to make the back button disappear or something.

I don't think there's been a single moment where I've just been in the flow of writing code. Pretty much all of the process is grafting boilerplate into it.

Not long til deadline, thank fuck.

Comments
  • 3
    I feel your struggle :)

    as for the contexts -- bear in mind that the jvm is jugling tens or hundreds of contexts with separate classloaders [or more]. Even if you're simply passing a dumb value to it, it still has the right references needed to switch/suspend/resume/invoke/evaluate tasks in the background.

    It looks dumb. But makes sense with a platform this wide
  • 5
    @netikras I do get the context part, but the implementation is still ridiculous - my real gripe is with the amount you have to do to achieve anything. You need to make an new XML file every time you want to fart, you end up with loads of extra tabs not for the normal 'forgetting to close them' but because you actually need about a dozen open to be productive. The amount of setup is more like what you'd expect writing native code, but you're stuck with a very verbose Java API.

    The workflow is insane, and what you might earmark as a trivial task ends up taking half an hour of fruitless searching because the alpha parameter turns out to be called apparentTransparencyOnANormalScreenToSomeoneWhoCanSee or whatever.
Add Comment