Android is worse — it limits number of methods to 65535 (but has hacks to workaround it) https://developer.android.com/studio/build/multidex.html
A coworker mentioned that multidexing also take ages and uses huge amounts of memory.
65535 interfaces ought to be enough for anybody
11–20 of 82 posts
Re: 65535 interfaces ought to be enough for anybody
#12Any time you have a 16-bit count, it won't be enough. It's a dangerous size...
Re: 65535 interfaces ought to be enough for anybody
#13Android is worse — it limits number of methods to 65535 (but has hacks to workaround it) https://developer.android.com/studio/build/multidex.html
A coworker mentioned that multidexing also take ages and uses huge amounts of memory.
Are there any legitimate use cases for that many methods?
Re: 65535 interfaces ought to be enough for anybody
#14Any time you have a 16-bit count, it won't be enough. It's a dangerous size...
The same is true of 32 bit numbers. 64 bits might finally be enough. crosses fingers
Re: 65535 interfaces ought to be enough for anybody
#15Earlier quoted context omitted.
A coworker mentioned that multidexing also take ages and uses huge amounts of memory.
Are there any legitimate use cases for that many methods?
I mean, it means you can't pull in Scala. I mean, you can, but pull in enough bloated Java 3rd party libraries and you might be hitting that limit pretty quickly. Google broke Google Play Services out into a large number of small dependencies once they were past the 15k method mark. Mind you, certain compilation settings will totally strip out unused methods, but it's still annoying.
Re: 65535 interfaces ought to be enough for anybody
#16Earlier quoted context omitted.
A coworker mentioned that multidexing also take ages and uses huge amounts of memory.
Are there any legitimate use cases for that many methods?
IIRC the Facebook app had many more than that at one point, and had to use multi-dexing. Not sure if that's still the case.
I've also heard that scala apps on Android can sometimes hit the limit, because pulling in the scala stdlib greatly bloats the method count.
Re: 65535 interfaces ought to be enough for anybody
#17Earlier quoted context omitted.
Are there any legitimate use cases for that many methods?
IIRC the Facebook app had many more than that at one point, and had to use multi-dexing. Not sure if that's still the case. I've also heard that scala apps on Android can sometimes hit the limit, because pulling in the scala stdlib greatly bloats the method count.
Wasn't that the initial reason behind splitting off Messenger into a separate app?
Re: 65535 interfaces ought to be enough for anybody
#18File this under 'premature optimization bites after 12 years'.
Re: 65535 interfaces ought to be enough for anybody
#19Android is worse — it limits number of methods to 65535 (but has hacks to workaround it) https://developer.android.com/studio/build/multidex.html
A coworker mentioned that multidexing also take ages and uses huge amounts of memory.
Why do people always talk about multidexing like it's such a nightmare?
https://developer.android.com/studio/build/multidex.html
It's really not that bad, It only gets a little squirrely if you're trying to support super old android versions.