5 ms·
Because you want to use a library that was written for Node and not speed time finding (or writing) something similar for the JVM? If you know Node better than
by emidln 13y ago
Because you want to use a library that was written for Node and not speed time finding (or writing) something similar for the JVM? If you know Node better than the JVM, Clojurescript on Node is very likely more valuable to you when starting out than Clojure on the JVM.
- leishulang 13y agonot to mention that node-webkit will enable clojurescript to be a major player in large desktop production tools (light-table).
- pjmlp 13y agoJavaFX, Swing, AWT, SWT, Windows Forms, WPF, XAML,.... Webkit, blah.
- leishulang 13y agowebkit might be so so. with node in the formula, and all those npm goodness, I don't think the ones you mention are as nice and as open.
- pjmlp 13y agoGiven JVM and CLR's age, I doubt there is any library for node that doesn't already exist in a similar way for the other platforms.
- emidln 13y agoJust because a library exists for the JVM or CLR doesn't mean a person familiar with Node knows that it exists or the advantages/disadvantages of the 15 libraries that will show up for any given thing they are trying to do. The libraries, profiling tools, performance tuning details. These are the things that make up a platform. Knowing the syntax of Clojure and nothing about the JVM ecosystem isn't going to help you ship any faster. Should a developer in this situation bite the bullet and learn a better supported platform? Maybe. Does everyone have time to do so? Probably not.
- pjmlp 13y agoSince Clojure was born in the JVM, I doubt anyone learning Clojure will be more at home in node.