Hi Ed, I will try to answer your questions.
1. Indeed, the AOT compiler will create performance optimized JS from the templates. JSX is the other way around, it creates HTML from a javascript mixed with HTML like syntax. Please note, that the resulting JS files are build for performance in the browser, and also to have the smallest footprint possible. The AOT compiler can do this better as the JIT, because it can use more time to optimize for the optimal result. 2. In normal situation optiong for AOT is the smart thing to do. During development it will come in handy when during the creation time of a component. However, you might have an backend that will dynamically creates templates. In this case one might prefer the JIT. However, the backend might also be able to use the AOT on those templates, and just serve scripts, but this is an scenario that justifies the use of the JIT. Quick prototypes are also a good candidate. Setting up a AOT build step, is an extra thing you need to setup, might not be worth the trouble in prototypes and/or proof of concepts. 3, Yes, split this up in separate modules. also split out the common code to another separate module, that can called in by all of them. By doing so, you enable the possibility of lazy loading, and if one of the modules outgrouws your project, you can easily split it out to it's own project. Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
