On Friday, May 12, 2017 at 1:55:24 AM UTC-7, Thomas Heller wrote: > I'm way too biased towards the Closure Compiler and giving that up is simply > not an option for me. I am however very interested in making things simpler > for everyone. > > https://github.com/thheller/shadow-devtools/wiki/ClojureScript-for-node.js-libraries >
This looks very nice, with a colleague here we event went as far as thinking, what if we completely drop GCP support for node.js targets. We talked about this a bit on Clojurians, I like your idea to get closer to the node way. I am not a JS dev at all, but I understand the pain of existing JS devs when they approach the ClojureScript world. They need to change everything they know, not only learn a language but also new (JVM) tooling. Many say no thanks, which is a pity because they are missing out :D I have recently worked on a POC using Reason. The tooling is rough but it fits the JS ecosystem. The compiler is super fast (faster than Typescript even on my machine!). We ended up picking Typescript because of the tooling basically for a zero version of our stuff. I already don't like it that much ah ah. -- 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at https://groups.google.com/group/clojurescript.
