@micha: what is the rationale behind the newly-introduced --refers option in boot-hoplon - why do we need another mechanism for magically injecting dependencies instead of simply mandating that jQuery be loaded from cljsjs as a :provided dependency? i'm sure you have a good reason, but i'm curious to know what it is.

@jumblerg firstly for compatibility with previous versions of hoplon

other than that you do not have to use it

like personally i use it for injecting my logging macros

so if i want to log something i can use the logging macros that don't emit code for production

so i can put logging wherever i want without needing to remove it in prod

eliminating the extra step of :require the namespace etc means that i don't just use console log to quickly get some logging, which is what i would do if i didn't use --refers

@jumblerg also it's not a dependency issue, because jquery is always a dependency of hoplon, that hasn't changed

what the --refers stuff does is refer hoplon.jquery namespace into .hl pages

that installs the do! and on! multimethods that use jquery

the hoplon.goog namespace installs do! and on! multimethods that use google closure instead

:thumbsup: good summary!

a wild paul appears!

@alandipert heh; i haven't done web-dev for serious in awhile and I'm probably doing terrible things, but hoplon's workflow is just killer

I've got some refinements to make before it's prod-ready, but we'll be deploying that on our mesos hosts soon

0147eb8a-cc66-404a-b053-0cbf4e44061d

a gift, for your collection