Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail From: Ali Arif Newsgroups: comp.lang.java.programmer Subject: Re: I need a Android Programmer Date: Thu, 20 Feb 2014 01:04:08 +1100 Organization: Aioe.org NNTP Server Lines: 86 Message-ID: References: <1vwyca145du6l.1a85pdmp3xzw1.dlg@40tude.net> NNTP-Posting-Host: txrwmXI+5Ffa2GxFsf5Wvg.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Unison/2.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:27553 Hello, > Ali Arif wrote: >>>> Ali Arif wrote: >>>>> Until NDK (C++) arrive, only moron program the Android. > > Such horseshit. > >> Whoever wrote that was truly a moron. Today, huge populations of > > You're a piece of work, aren't you, Ali? Why thank you. I return the compliment. > >> computers run either IOS or Android and their numbers are growing >> rapidly. Only a moron would write an application for Android in Java > > You keep using that word. I don't think it means what you think it means. > > You *do* realize that Android was designed to be programmed in Java, do > you not? > > Java is the native language of Android. Only a moron wouldn't realize that. Are you arguing that one cannot write Android code in C++? One merely has to tolerate having load the C++ code with a jni Activity adapter and some jni event glue. Game over. > >> as that would mean that it would have to be rewritten for IOS. By > > Well, duh. The platforms are radically different! Of course apps from > one platform > have to be rewritten for the other. That's an architecture issue, and > the language > makes no difference there, as anyone but a moron would know. Yawn. Of course the platforms are different, that is why one would try to ensure that the bulk of the logic is in a common code base independent of the platform. Naturally the portable C++ code contains its own event dispatching and UI rendering (which is done with OpenGL in 2D mode). You can render precisely the same UI on IOS or Android and algorithmically adapt to a device's screen resolution. > >> using the NDK you can write most of the functionality in a C++ code >> base shared with IOS and only use Java or Obj-C only when necessary to > > You *do* realize that Objective C is the native language of the iOS > platform, right? > Only a moron wouldn't realize that. You appear not to know that IOS native code is compiled with Clang which out of the box supports C, Obj-C and C++. In fact one can freely mix all three in the same source code module. You obviously have no experience in this but feel compelled to voice your ignorance regardless. Oh well. > >> bootsrap the C++ stuff. Performance is benefited too in the case of >> Android. > > Bullshit. Oh I see. Let's suppose that one of the jobs of your application is to process 44.1kHz audio data from multiple concurrent audio sources (tracks) and perform some transformation on the data (like a convolution, delay or filter), and then pass the audio to the sound driver. You will also need to render a UI with stuff like real time VU meters and keep up with the video refresh rate. I sure as hell don't want to be doing that in Java on a relatively piss-weak ARM CPU 'cuz you're going to hear lots of clicks and pops and stuttering. Ali Arif