On Mar 6, 7:46 am, Luke VanderHart <luke.vanderh...@gmail.com> wrote: > The biggest barrier to using Clojure in an "enterprise" environment is > that enterprise projects are typically built and maintained by 100s of > replaceable code-monkeys and consultants, all of which understand Java > and almost none of which understand Lisp of any kind, let alone > Clojure.
That's why Clojure has JVM interoperability ;-P Think of Clojure as an embedded higher-level language running within Java. You can hide it completely with a Java wrapper so that nobody has to read or write Clojure code but the local Clojure expert(s). We do this all the time with C and Fortran: we only require our libraries' users to know C or Fortran, but we embed Lua and ANSI Common Lisp (via ECL) in our libraries to do harder coding tasks, and use other scripting languages to generate code. All those other languages are hidden from the users. A well-written library treats other programmers on the team as "users" who don't have to know the internals of the library. mfh --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
