Re:Ionic – A front-end framework for developing hybrid mobil...
by somethingnew on Friday November 22, 2013 @02:54PM
(#6783321)
As a funny relevant aside http://vanilla-js.com/
Re:Ionic – A front-end framework for developing hybrid mobil...
by coderzach on Friday November 22, 2013 @10:38AM
(#6781329)
It sometimes work well on mobile. I think the best approach is to build it in jQuery, if it doesn't perform well, figure out what's slow and replace it with pure DOM.
This generally results in replacing some jQuery calls in methods that get called a lot, e.g. touchmove, requestAnimationFrame, etc.
Re:Ionic – A front-end framework for developing hybrid mobil...
by Cthulhu_ on Friday November 22, 2013 @10:00AM
(#6781044)
Well, according to small tests, jquery's selectors are slower than the 'native' selectors; findElementById for example is at least twice as fast as jquery's $('#someId') call. But that's because jquery has to parse the query first.
It's a productivity versus performance thing, really. Native JS is often faster than the same thing in jquery.
Re:Ionic – A front-end framework for developing hybrid mobil...
by domrdy on Friday November 22, 2013 @10:24AM
(#6781196)
Here's a relevant test: http://jsperf.com/queryselectorall-vs-jquery-jb
Re:Ionic – A front-end framework for developing hybrid mobil...
by adamdbradley on Friday November 22, 2013 @10:11AM
(#6781111)
You could still include jQuery in your app if you wanted to. However, the Ionic framework itself does not run on top of that extra layer, especially when native javascript and hardware accelerated CSS transitions will be faster.
>zero jQuery
Perhaps I've not been keeping up with the latest JavaScript news but is jQuery considered slow? jQuery 2 is a lot lighter and works well on mobiles.