31–40 of 82 posts
Earlier quoted context omitted.
why use the cloud though? just build on premise and use existing MDM, or App Store
Right, AFAIK the framework itself functions independently of the services, so you can drop in whatever solution you want for push notifs / analytics / MDM.
Ionic 2 is much more performant and scales much better for app development than Ionic 1. I have yet to meet anyone who has not really enjoyed developing Ionic 2 apps. We take a tremendous amount of pride in the developer experience!
Native apps will always be a little faster but if you can get 60FPS either way, who cares? Ionic is easier to build apps with, and developing in the browser is a joy.
A huge advantage of Ionic is being able to deploy the same code base to the web as a PWA and to a phone natively as a cordova app. Soon Ionic Native will expand to support PWA and Electron, too, so it will truly be a write once run anywhere experience.
http://ionicframework.com/docs/v2/components/#overview
,while Angular 2's official material design components are still in the pre-release stage:
https://github.com/angular/material2
Good job on filling the gap for Angular 2.
What's the equivalent for desktop site development?
Earlier quoted context omitted.
Right, AFAIK the framework itself functions independently of the services, so you can drop in whatever solution you want for push notifs / analytics / MDM.
that is what we do in our organization, we don't see value on their cloud services, we see value on their framework
Key point - for hybrid development. There are a lot of use cases where hybrid mobile apps are appropriate (CRUD). With ever more powerful devices, the argument for hybrid increases.
"complex" and "object oriented" does not describe any future of JavaScript that I am excited about.
I think it's around 5 years too late to prevent the complexity explosion :) JS has been object oriented since the beginning it just has an insane prototype based inheritance hierarchy that they're increasingly trying to hide/pave over.
Think subreddits for NPM.
"complex" and "object oriented" does not describe any future of JavaScript that I am excited about.
Type systems (e.g. TypeScript) expose complexity well. Maybe I don't understand your comment - are you writing only simple apps which don't use objects?
Yes and no. With Typescript, js developers tend to write js code like they would write Java code, in all its verbosity. They don't need to, but they do.