.@RichFelker Two basic complaints with BeOS in 1997: 1) the fragile base class problem, which they solved by padding public C++ classes.
-
-
.
@RichFelker So very true. Android was also "the revenge of Danger", since so many early engineers came from there. https://en.wikipedia.org/wiki/Danger_Hiptop … -
I was an intern at Be for 6 months in 1997, but I worked at Danger from 2005–2009. Android is basically open-source Danger OS.
@RichFelker -
The same engineer who designed Dalvik also worked on Danger's JVM (with a similar proprietary bytecode) before joining Google.
@RichFelker -
.
@RichFelker Android switched from Dalvik to ART, an ahead-of-time compiler known for making "Upgrading app X of Y…" waits take even longer. -
.
@RichFelker Dan Bornstein gave some good public talks circa 2009 on why Dalvik and .dex files are the way they are. https://en.wikipedia.org/wiki/Dalvik_%28software%29 … -
.
@RichFelker Dalvik's bytecode was designed for fast interpretation by an optimized interpreter, which Danger and early Android both used. -
.
@RichFelker I remember thinking Android had a better strategy than Apple, but I didn't know Apple's roadmap had so much cool stuff on it. -
.
@RichFelker The good thing about Java is it's a "safe" language with exceptions & full stack traces in the log when something fails. - 3 more replies
New conversation -
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.