NativeScript – Cross-platform framework for building native mobile applications

Re:NativeScript – Cross-platform framework for building nati... by jerf on Friday June 13, 2014 @12:10PM (#7889534)

That's call asm.js. asm.js is just a bytecode with a particularly baroque serialization right now; if it is widely adopted expect a more compact serialization to be one of the first "optimizations" released.

asm.js is a really clever play to leverage Javascript to get JS out of the way, while never making it obvious that's what it's doing.

[ Parent | on HN ]

Re:NativeScript – Cross-platform framework for building nati... by CmonDev on Friday June 13, 2014 @12:11PM (#7889544)

That's the only hope. Unfortunately there is so little news on that front and no enthusiasm from the side of mainstream language providers so far...

[ Parent | on HN ]

Re:NativeScript – Cross-platform framework for building nati... by Rusky on Friday June 13, 2014 @01:10PM (#7889812)

asm.js is still stuck with the JavaScript memory model and type system no matter how it's serialized. I would almost be okay with a textual serialization of a language with better semantics.

[ Parent | on HN ]

Re:NativeScript – Cross-platform framework for building nati... by vertex-four on Friday June 13, 2014 @03:53PM (#7890546)

> asm.js is still stuck with the JavaScript memory model and type system no matter how it's serialized.

What? You're stuck dealing with ints and a heap of memory... which is exactly what you get when developing native code. On top of that, you can implement any memory model and type system you want.

Are you saying you want a managed VM, so something further away from the processor? What features do you want, and which tradeoffs would it make? Why can't you just implement your managed VM on top of asm.js?

[ Parent | on HN ]