int3/jsshaper — comment on commit c18505c090d582671f715621290f2f0d19a65fe2
File:  line 0
By olov:

@cscott Alright. I've been trying to wrap my head around AMD and as far as I understand, this seems pretty good. Thanks a whole lot for the effort of AMD'ifying the code base by the way. There are things I like with AMD, such as that it works well with node.js with a little bit of ceremony. I dislike the increased scope-level (hidden or not) in most of the code base.

What I'd like to understand before we go all-in on AMD, is what drawbacks the alternative route, i.e. going all in on CommonJS/node.js require with or without triplets, would have for your use-case? It already works in the browser (although dependencies needs to be spelled out explicitly in form of a set of script tags), albeit not in any asynchronous loading fashion. I assume that there are tools available to combine multiple CommonJS modules for the browser more intelligently than just concatenating them as I've done. Perhaps even tools that convert CommonJS require's to AMD define's.

Does AMD fit well with the node.js community? I want to make sure that now that we drop support for d8, js and possibly rhino, we end up with something that fits the node.js culture as well as possible.