Hacker News Reader

Not a problem at all, that is just the typical Java FUD and bad coded apps.

The real time audio APIs are in native code and they can request for priority use when on foreground.

Samsung used to support real time audio on their S models since many years.

https://developer.samsung.com/galaxy/professional-audio

Which they are now deprecating as they also contributed to the design of AAudio.

I can "feel" the lag in the android experience and it's the same lag that I get from desktop apps written in java. It's not just FUD. Almost always when there's a memory-bloated application it's written in java. Hell, adk won't even run unless you increase the -Xmms setting to 4+ gb.

People rightfully pointed out that tablets are plenty powerful to do DSP type applications, but something is consuming all the resources. I'm just saying what that something is.

Don't confuse the language with the ability to program.

I lost count the amount of times I have fixed junior code doing what should be background stuff written on the main thread, for loops instead of System.arraycopy, allocating memory in loops and lots of other stuff due to lack of proper teaching.

As for Android, the real time audio stack is fully native and Google had to learn from Samsung how to do it properly.

Reply on news.ycombinator.com