News for hackers. Stuff that matters.
Re:Why Trigger.io doesn’t use PhoneGap – 5x faster native br... by newhouseb on Friday February 24, 2012 @02:48PM (#3630688)
> Also, I can absolutely see the need to send large number of messages - a streaming accelerometer API, for example, which is on our roadmap.

There is no benefit to sending ondevicemotion events out to the native code because you can always get higher frequency updates on the native code (60Hz vs 20Hz) and sending them in via stringViaEvaluatingJavascriptFromString is identical between Trigger.io and PhoneGap (and will happen with a lower latency than things are drawn on screen in a UIWebView).

Re:Why Trigger.io doesn’t use PhoneGap – 5x faster native br... by jamesbrady on Friday February 24, 2012 @03:55PM (#3630971)
Yep, I was referring more to native accelerometer events being fed into the web view.

True enough that on iOS we would perform comparably, but for Android, it would mean "long"-polling a local web server at 60Hz!

Re:Why Trigger.io doesn’t use PhoneGap – 5x faster native br... by utopkara on Saturday February 25, 2012 @06:43AM (#3632739)
And, this half-baked reason was the example that James can give off the top of his head for not using PhoneGap.