Macros are just a completely different topic from the original post. Separating the macro system from runtime means you don't have 2.5mb of JavaScript which can't be dead code eliminated when you start writing a simple client application.
David On Tue, Dec 6, 2016 at 6:21 PM, mars0i <[email protected]> wrote: > On Tuesday, December 6, 2016 at 11:31:59 AM UTC-6, David Nolen wrote: > > Yes we are aware of this and we do not intend to pursue since it offers > nothing in the way of real benefits. > > > > > > It does seem potentially useful to third party efforts around > bootstrapped ClojureScript, but that's about it. > > I don't have an understanding of the tradeoffs involved, but given the > little bit of semantic and practical funkiness involved in macros being > compiled in Clojure and run in Clojurescript, I would have thought that > moving to an all Javascript/Clojurescript system could possibly be a good > thing in the long run. > > -- > 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 https://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 https://groups.google.com/group/clojurescript.
