Good advice; I've used dependency injection when building shared backbone views that need to initialize different client-side libraries. I'm not a fan of AMD in general; I think the app should be delivered complete in one request, so that over high-bandwidth/high-latency networks like 3g/4g/lte mobile the experience remains fluid (no waiting for that last library to load). I guess it depends on your environment.
On Monday, February 25, 2013 6:58:09 PM UTC-5, Bradley Meck wrote: > > Generally I abstract out my implementations and my interfaces. This means > a more verbose code base, but allows me to have the renderer inserted via > dependency injection. It is independent of bundling tech and I have used it > with browserify as well as with AMD to great success. Decoupling those > allows you to reuse interfaces on server side, but implementations will > always need rewriting. If you do dep injection though only the renderer > generally needs a rewrite though which is a huge win. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
