octalfudge@lemmy.world to Apple@lemmy.worldEnglish · edit-22 years agoPossible explanation for jank in Android as opposed to iOS (20 millisecond core ramp on ARM/Android vs 50 microseconds on Apple/iOS)social.treehouse.systemsexternal-linkmessage-square28fedilinkarrow-up183arrow-down18file-text
arrow-up175arrow-down1external-linkPossible explanation for jank in Android as opposed to iOS (20 millisecond core ramp on ARM/Android vs 50 microseconds on Apple/iOS)social.treehouse.systemsoctalfudge@lemmy.world to Apple@lemmy.worldEnglish · edit-22 years agomessage-square28fedilinkfile-text
minus-squarehuginn@feddit.itlinkfedilinkarrow-up3arrow-down1·2 years agoI can use the exact same apache jars on my Android project and my Java server. That’s not Python. That’s very clearly java code. The implementation of the contract is different but that’s not the same as not being Java.
minus-squarehuginn@feddit.itlinkfedilinkarrow-up1arrow-down1·2 years agoYou absolutely can pull the same jars into server and android projects. Sometimes you need a different one for Android to avoid NoClassDefFoundErrors but you’re totally able to grab a jar and stick it directly into both sides.
minus-squareAux@lemmy.worldlinkfedilinkarrow-up1arrow-down1·2 years agoThe hell are you even talking about? You can’t even load a JAR file on Android. My god…
I can use the exact same apache jars on my Android project and my Java server.
That’s not Python. That’s very clearly java code.
The implementation of the contract is different but that’s not the same as not being Java.
You can’t use the same JARs in runtime.
You absolutely can pull the same jars into server and android projects.
Sometimes you need a different one for Android to avoid NoClassDefFoundErrors but you’re totally able to grab a jar and stick it directly into both sides.
The hell are you even talking about? You can’t even load a JAR file on Android. My god…