On 27 July 2011 01:43, Mark Derricutt <m...@talios.com> wrote: > My unhappiness with it is more akin to my unhappiness with ANY language that > tries to target multiple VM platforms, and that's mostly due to the > -potential- to break the community.
It may be helpful to approach the issue with the premise that ClojureScript != Clojure. They share a lot of syntax and semantics, and a developer experienced in one can easily transfer his/her working knowledge to the other. But in the end, I perceive them as two different languages that just happen to have a lot in common. > Enter ClojureScript, for the most part you will be able to reuse server code > on the > front end, but some of those libraries you've become accustomed to using just > won't work, and if you're working to a deadline and suddenly hit that - you're > going to become frustrated beyond all hell ;-) Personally, I wouldn't assume that anything works on ClojureScript unless explicitly tested and labeled as such. This seems like an interesting avenue to follow. This thread is already past its expiry date, though, so I doubt further discussion will get much attention here. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
