You understood my question. Thanks for the insight. On Friday, August 14, 2015 at 1:42:40 PM UTC-7, Linus Ericsson wrote: > I'm not sure if I understand your question, but there's no apparent way > clojure.browser.dom would make any sense since it doesn't (or at least > didn't) map to any specific JVM host language feature, but was very relevant > in clojurescript, at least in the pre-react era. > > The stranger part is probably that some libraries are name for instance > clojure.core.async and cljs.core.async for the different hosts. With the new > conditional readers in 1.7.0 I think we could expect these libraries will > harmonize the nameing to clojure.core... > > /Linus > > Just curious. > > > > There are several ClojureScript namespaces that begin with "clojure" that are > available in both Clojure and ClojureScript, for example clojure.set and > clojure.string. > > > > Then there are namespaces like clojure.browser.dom that do not have a > corresponding namespace in Clojure. > > > > Why the difference? > > > > -- > > 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.
-- 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.
