Apping gone horribly wrong

file:/// wait, no, it's https://developer.android.com/tools/building/multidex.html Building Apps with Over 65K Methods
Over 65K Methods!
What the fuck could take 65K methods to accomplish?!? According to https://msdn.microsoft.com/en-us/library/windows/apps/dn424765.aspx, there are 3149 functions in the entire windows API. You could implement the entirety of Windows twenty times over, and that's not enough for a single app? What the fuck is going on? Naturally, it's Java that's to blame, and it's retarded obsession with class oriented programming. I'm guessing that there are dickload of getters and setters that are never more complicated than single line assignments or return statements, but never the less cannot be inlined because of some retarded object model in the JVM.

Also, why the fuck does the offline documentation for Android phone home to Google every, like, five minutes? Did they think I wouldn't notice? What do they even hope to gain?

>>6
That's the thing; they probably aren't. dex is just a piece of shit for needing to assign a 16 bit ID to every method in the application, including ones that aren't ever called. A better system would attempt to assign such short IDs only for methods it can deduce will be called frequently, and use longer ones for the rest, with a dynamic optimizer to distinguish between the two.