Re:Converting an existing Backbone.js project to Require.js
by jafaku on Thursday August 29, 2013 @04:02AM
(#6294774)
Wtf, who said anything about a 10k LoC js file?
"possibilistic" said dependency resolution must be done at compile time:
> I don't want any dependency resolution code in the production build, because that's a problem that needs to be solved at compile time.
Re:Converting an existing Backbone.js project to Require.js
by codeonfire on Sunday September 01, 2013 @10:41AM
(#6310545)
The tool that is mentioned, grunt, appears to resolve dependencies at the package level, not at the module/file level. Dependencies at the package level with no module level resolution tend to cause very large source files because no one is going to make a new package for each unit of code.
The god-file approach to development leads to things like lots of search and replace when something needs renamed, name collision, and duplicated utility code everywhere.