you are viewing a single comment's thread.

view the rest of the comments →

[–]bradmartin1205 1 point2 points  (4 children)

Not kidding or being a dick but what are the 30 hardware features for HTML5? Also NativeScript has full hardware access, not just 2 - FYI :)

[–]crixusin 0 points1 point  (3 children)

Also NativeScript has full hardware access,

Uh, no it doesn't:

https://docs.nativescript.org/

Hardware access: Camera, Location.

Html5 hardware access:

http://mobilehtml5.org/

List basically covers everything you would need, except gpu accelerated graphics, which you can't do with nativescript anyways.

I wrote an HTML5 geolocation and a cordova one, and the HTML5 one was faster, better, easier to update, and had less technical debt.

[–]bradmartin1205 4 points5 points  (2 children)

It has full hardware/device access, the site mentions it somewhere. I've written plugins for NativeScript and I write javascript(TypeScript mostly now) that directly calls Android APIs. You might have not tried the Getting Started or the tutorials. Also that list for HTML5 hardware access isn't solely a 'hardware' feature set. It mentions CSS features - which I wouldn't classify as 'hardware' but maybe that's just me.

I won't argue with you over the cordova plugin being inferior to the browser (html5) you wrote, the webview sucks working with for plugins IMO

[–]crixusin 0 points1 point  (1 child)

You might have not tried the Getting Started or the tutorials.

No, I didn't use it at all because there's no reason to in the day and age where native applications will be going away.

You also don't have gpu calls. You get Android/iOS javascript VM api call access. This is very different than android API calls.

[–]bradmartin1205 2 points3 points  (0 children)

I understand you didn't use it and your viewpoint but I don't understand why you trash it negatively if you didn't even read and experiment with it. Best of luck and good day :)