Can the Android platform and its toolchain outrun the language toolchain killing compatibility behind it? Tune in next year to find out.https://twitter.com/jddarcy/status/1017574880210849792 …
Show this thread
Want a free question to ask on the Reddit AMA next week? This is it: how do you reconcile a language and bytecode whose development has kickstarted into high gear with a platform that ships at half the rate. And if you think the answer is Kotlin you haven't been paying attention.
-
-
Desugar the planet.
-
True, but that only solves the language feature part. We're still stuck without the APIs. Bazel (and hopefully D8 in the future) is trying to solve that by bundling those APIs as a companion dex, but even that can probably only go so far when the features rely on VM changes.
-
That's a nice approach. Ideally a single dex companion on the platform (updated by play services?) would be mapped into multiple processes to avoid bloating each installed APK like we do now with the Kotlin stdlib & runtime. Nested VMs (VMVM) might get us over that last hurdle.
-
Yep. All things worth exploring (and I hope someone already is). The biggest downside that I see there is that it might mean the framework can't use those new features and API. Not sure.
End of conversation
New conversation -
-
-
Is the solution to quit Android development, close my laptop, walk to the lake, throw the laptop into the lake, take a one way bus ride to the Appellations and live out my days living off the land?
-
I will if you will.
End of conversation
New conversation -
-
-
Are you not able to post questions to the AMA?
-
I mean I guess I could…
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Don't. Fork the bytecode format
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.