Hi Leo, I like your idea of using git subtree. This lets you build your applications out of small building blocks. You need a good style-guide and your team needs to take in account that modifying a component might break something else. Aside from that, it is a good way to incorporate reusable parts in your projects.
I highly dislike the requireJS idea. I firmly believe you should use a build step that creates a single file output. If you don't want to deliver security sensible code to all users, build different versions (exclude the code out of the build that you don't want to ship) If your code-base becomes extremely large, you might split it up in a few parts that you might load when needed. Let me tell you what I think what extremely large is. If you concatenate and minify all your code, and the gzipped result of that is larger then 250Kb(for web) or larger than 1Mb(for in-house stuff) Of coarse, sometimes you want to split up things, for that you can use commonJS modules (as supported by angular itself since 1.4), or implement a ES6 module loader. This way, your code-base is ready for the future. Then let your build tool build them. On more thing, in your blog post, you are creating a config that is away in another module. In this module you explicitly name the resource the config is for. Isn't this defeating the purpose? If it is that thightly coupled, should it be in the module it is intended for? If not, why bother with the coupling. For all I know, an Mb is an Mb for every purpose? 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 http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
