Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
transitioning to angular 2 / ionic 2 stack #403
*Update* from me below!!
new collective ticket for all topics angular 2 / ionic 2.
1 similar comment
Update December 21st, 2016 - slow development for Angular 2 & Ionic 2
Hey gals and guys.
I think it's time we give you guys some more information on what's been going on in the past weeks and months. You haven't heard from us in a while and you deserve to be provided with some insights in what's been going on.
We've been working on a version for Angular 2 & Ionic 2 for quite some time now, we built prototypes to test setups, tools, and ideas and invested a lot of time in research. Unfortunately, we're not making progress as quickly as we hoped. There is a variety of reasons for that: With Typescript, RxJS, ES6 Angular 2 has a very steep learning curve and so internally at M-Way it turns out to be very daunting for our developers. Thus we're not adopting it as quickly as we thought and on many occasions, we're not yet sure what we want and need. On the technical side of things, which you are probably more interested in, also lie many obstacles that currently impede development. I will try to explain them in the following, without boring you with the details too much:
The biggest obstacle is probably that the setup for Angular 2 alone is incredibly complex already, even without adding Ionic 2 and Cordova. So apart from the already complex workflows of Generator-M-Ionic there are now many additional topics to consider: like module loading and bundling, ahead-of-time AOT compilation, lazy loading, typescript transpilation and source mapping. With that, just getting your setup to perform a proper build of your project is a very complicated task, not to mention trying to add all the advanced workflows Generator-M-Ionic currently provides.
Many inter-dependent options and lack of interoperability
It's not just very complicated, there are also many many different tools to accomplish these tasks, with different states of stability, maturity and different sets of interoperability and dependencies. Furthermore, some of these still feel very beta and it's just very burdensome to build complex setups with them.
There's an incredible amount of options and variables to consider. Do we use SystemJS to load bundles, as it's recommended on angular.io? That would work well with a gulp setup, possibly easier to integrate with AOT which needs to compile your Angular Code using the
Thus. Long story short: We could throw together a dirty, not well thought-through version for Angular 2 and Ionic 2 quickly, right now and publish it. But that's not what we want and we don't think that's what you want, either. We've invested a lot of time, effort, and money to make Generator-M-Ionic a high quality, professional tool for us and for everybody who wants to use it. We use it every day, with pleasure and I'm sure many of you do as well, so we just don't think anybody would benefit from a half-baked, buggy and inconsistent setup. There's enough of those out there already.
So what can you do now? - Hang on, join the discussion or report back with your experiences while developing with Angular 2 / Ionic 2: webpack, aot, gulp, rollup, whatever, ...
I'll try to keep you updated more regularly, probably simply by commenting more on this issue.
Let us know what you think.
referenced this issue
Jan 18, 2017
referenced this issue
Jan 27, 2017
@gruppjo thanks for the great generator. I really appreciate the effort you guys have put into it and support your approach as well as the quality standard you want to maintain with the V2 of this generator. It's better this way than to make it work halfway and then spend your time fixing/boilerplate-coding.