Thanks for your feedback. The primary use case that drove this project was 
wanting to ship an Om wrapper around Codemirror, but not have to include a 
bunch of instructions in the README telling the user how to pull in the 5 
different JS/CSS Codemirror files, which would change every time I wanted to 
update the Codemirror version. The alleviates all that hassle and let's me, the 
library author, manage it, not the users.

> I think at the limit case (not all projects go to this degree) people end up 
> wanting something like this: Minify and combine all of the asset JavaScript 
> and CSS into one file each. Minify all the application JavaScript and CSS 
> into another file each.
> 
> 
> 
> Another variation some projects prefer: combine the above so you only have 
> one JavaScript and one CSS file.
> 
> 
> 
> Another variation some projects have found better in the real world: peel out 
> a few of the largest libraries, and load them from somebody else’s CDN 
> instead. The user might already have them cached, and even if they don’t, 
> they load using bit somebody else paid for.
> 
> 
> 
> At the same time, during development is much more convenient to not combine 
> things into one file, but to instead spray a bunch of script tags. That way 
> when you are using the browser development tools, you directly see what file 
> the various bits of JavaScript really came from. Also of course, during 
> development one does not want minified libraries. (Every once in a while I 
> see someone trying to do development using combined and minified files… not 
> an efficient use of time.)
> 
> 
> 
> From a quick look at your library, it seems like it is a step in the 
> direction of being able to do these things. My sense is that over time your 
> tool or a competing one will need to grow a set of knobs and switches to 
> accommodate these variations in people’s preferences about production 
> deployment, and production vs development. Of course today many projects use 
> a painfully complex ad hoc build process to do these things, there is so much 
> room to do it better, it is great to see your tool take a step!
> 
> 
> 
> 
> 
> --  
> 
> Kyle Cordes
> 
> http://kylecordes.com

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" 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/clojurescript.

Reply via email to