3 ms·
Author here. I agree with a lot of what you say. One thing: "everythings hidden behind a thick layer of abstraction". Native does just that! Abstracts a bunch o
by nwienert 12y ago
Author here. I agree with a lot of what you say. One thing: "everythings hidden behind a thick layer of abstraction". Native does just that! Abstracts a bunch of stuff away for you. It's just a different abtraction (and one you'll need to write three times for iOS/Android/m.web).
I also would like to see Facebook come back to the middle on this, a company that big could put a lot of resources into making those web to native APIs evolve and bridging the performance / feature gap of JS, an effort they are currently putting into bridging JS to C with mass amounts of developers.
- aikah 12y agoWell,Facebook is putting resources on React native which is totally sane given the fact that they want their mobile app to use a native GUI. Javascript is just a sugar to make development cycles faster when supporting multiple mobile Os. The problem with your framework,just like jQuery Mobile,SenchaTouch and the rest is that it doesn't look native by a long shot.
- nwienert 12y agoIt has a theme running on the demo that isn't the default "native" look. It's also alpha, I'm confident it will look 99% native within a few months. There was a huge amount of time put into making it feel more native than any other hybrid approach so far, and that's what's important. I'm excited to start exploring webworkers and optimizations to really bridge that gap.