4 ms·
It probably isn't the same issue that is causing the Leiningen slowdown, but as near as I can tell the really slow startup time is the main reason Clojure on An
by kcorbitt 12y ago
It probably isn't the same issue that is causing the Leiningen slowdown, but as near as I can tell the really slow startup time is the main reason Clojure on Android isn't currently a viable option. Which is too bad, because I'd love to see the Clojure community's take on Android development. I can imagine a UI framework spiritually similar to Facebook's ReactJS appearing and making everything so much cleaner. And with a Lisp like Clojure there would no longer be any reason to use XML for layout and Java for logic -- it could all be unified into one cohesive language. Maybe I'm dreaming too big, but that would be an exciting future.
- pjmlp 12y agoClojure is too slow, because of the vars creation that it does on startup. Work is ongoing to improve the situation for Clojure 1.7, but apparently the slowness won't go fully away. There as a post a few weeks ago on the mailing list about using ClojureScript instead, with compilation to Java bytecodes via Nashorn, before feeding the class files to Dalvik/ART. All of this is just too hacky for me. I would rather have a strong typed Clojure instead that wouldn't suffer from these pain points.