Timeline for Android differences (Dalvik+Java vs Old School C++)
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 29, 2022 at 23:00 | history | suggested | Glorfindel | CC BY-SA 4.0 |
2 broken links fixed, cf. https://meta.stackoverflow.com/a/406565/4751173
|
| Jun 29, 2022 at 18:13 | review | Suggested edits | |||
| S Jun 29, 2022 at 23:00 | |||||
| Aug 17, 2010 at 15:35 | vote | accept | Richard Fabian | ||
| Aug 17, 2010 at 15:17 | comment | added | brett | Oh, I see what you're getting at. Java has the bonus of having a massive standard library and an extremely competent library for dealing with XML. The Android platform extends the standard library with libraries for all of the fancy hardware goodies and some extra, user-side functionality. Java also supports incremental compilation/error checking, so you'll get feedback on errors pretty much as soon as you type them. Honestly, you shouldn't fear performance either. It's not going to be as fast as C on bare metal, but it's still quite speedy. I would say that there isn't much to worry about. | |
| Aug 17, 2010 at 15:08 | comment | added | Richard Fabian | thanks, "you can code in C/C++ on Android using the NDK", yeah I appreciate that, but why stick to old guns all the time if something actually turns out projects better / faster. | |
| Aug 17, 2010 at 15:03 | history | answered | brett | CC BY-SA 2.5 |