Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing Ionic 2 Final

blog.ionic.io

Post reply on HN
Print view View original

41–50 of 82 posts

Re: Announcing Ionic 2 Final

#41

Post by treehau5 »

79d697i6fdif wrote: post #14
erikpukinskis wrote: post #8

"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.

> just has an insane prototype based inheritance hierarchy that they're increasingly trying to hide/pave over.

Can you elaborate more on why you think it is insane? I think it is quite elegant, and in my experience they only try to hide or pave over it because just so many damn people can't get over the fact that it isn't classical object oriented

Also, for those who haven't read: http://javascript.crockford.com/inheritance.html

Re: Announcing Ionic 2 Final

#42

Post by MaxLegroom »

We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova plugin space. This, of course, is not the fault of the Ionic team, but it does create a frustrating development experience that played a large part in us abandoning it as an option.

This was also our first experience with Angular. I really wanted to like Angular, but after more than a year of development, we left it for greener pastures. I understand that Angular 2/Ionic 2 are touted as being significantly better, but while all those improvements were being made, we invested our efforts in learning and building with Swift. I can say that we are delighted with the outcome and have no real inclination to leave it for an alternative.

Re: Announcing Ionic 2 Final

#43

Post by jbmorgado »

danbucholtz wrote: post #33

Disclosure: I work on Ionic 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…

I was really very well impressed by the small size of ionic apps. It's in the order of ~3MB which is great.

But the startup times are somewhat big. I'm talking, for the simplest of applications a startup time of ~5.5 seconds in ionic 2 (the beta) vs ~2 seconds in React Native in Android.

For me, that detail has a significant impact in usability.

Any plans to work on those startup times?

Re: Announcing Ionic 2 Final

#44

Post by jgw96 »

jbmorgado wrote: post #43
danbucholtz wrote: post #33

Disclosure: I work on Ionic 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…

I was really very well impressed by the small size of ionic apps. It's in the order of ~3MB which is great. But the startup times are somewhat big. I'm talking, for the simplest of applications a startup time of ~5.5 seconds in ionic 2 (the beta) vs ~2 seconds in React Native in Android. For me, that detail has a significant impact in usability. Any plans to work on those startup times?

Disclosure: I also work at Ionic

So start up time is something that we are very focused on at the moment. Especially on the PWA side of things, TTI (time to interactive) is exceedingly important to ensure a good user experience. We are working on a few things at the moment but most likely the first one to hit is gonna be code splitting. So with code splitting, instead of shipping just one big bundle you will be shipping smaller bundles that are lazy loaded based on routes. This means that when the app first loads only the first bundle for the first view in your app will have to be loaded, parsed etc and then the other bundles will be lazy loaded. With this setup the browser (or webview) will never have to parse and load a huge bundle all in once, it will instead only have to deal with smaller bundles. This should give a pretty big improvement as parsing javascript is slow in every browser. From my testing on a moto g each MB of JavaScript in an ideal situation takes about 2 seconds to be parsed, so reducing the amount of JavaScript the browser has to deal with is a very fast way to get better load times.

Re: Announcing Ionic 2 Final

#45

Post by timrichard »

alexkavon wrote: post #26
EugeneOZ wrote: post #11

Earlier quoted context omitted.

You are wrong. I have few mobile apps, made with Ionic and Ionic 2, some have been used on warehouse as part of huge WMS (to scan items and manage whole business process of warehouse worker), some were apps for business as part of CRM (with geolocation, maps and handwritten signatures). And every time product owners were very satisfied with the result and with speed of development. Ionic 1 had too hacky API and not g…

I don't believe I ever mentioned ionic v2... I don't doubt v2 brought many improvements. However you just can't beat the power of not operating in a Webview.

However, Webviews do give you a very predictable container to target. If you use something like Intel Crosswalk [1] as part of your project for Android, you can bundle a recent Chromium webview to much older devices. And Flexbox is very well suited to solve phone/phablet/tablet layout problems.

[1] https://crosswalk-project.org/

Re: Announcing Ionic 2 Final

#46

Post by jbverschoor »

danbucholtz wrote: post #33

Disclosure: I work on Ionic 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…

Well unfortunately ionic2 is super slow to develop.. Ionic1 is nice in the beginning, but if your app grows, you're simply waiting and waiting. This is a problem with all javascript frameworks.. just 'watch' a directory for changes and restart, recompile everything

Re: Announcing Ionic 2 Final

#47

Post by jbverschoor »

jadbox wrote: post #32

I've been using react-native for the last year and can't say I have much positive to say about it. Honestly, just about every day we hit a sharp pain point in component layouts, broken build scripts due to RN bugs, and runtime crashes. While Ionic 2 is young, I welcome another option to the JS native space. I'm also hoping Flutter.io will get to a stable release.

Check out nativescript. It has 2 versions, one of which is angular2 based. It's pretty neat
Post reply on HN