swannodette

16 ms·

91.
by swannodette 11y ago
10 minutes? I'm sorry this is just FUD. I've seen very large ClojureScript projects that generate nearly 100,000 lines of JavaScript and even with advanced optimization (the slowest mode by far) I've never seen it take longer
92.
by swannodette 11y ago
Google Closure is not only a useful tool at the command line, it's also an incredibly powerful framework for manipulating, analyzing, checking, and producing JavaScript in a dizzying number of ways. And now thanks to Java 8's Nash
93.
by swannodette 11y ago
The Google Summer of Code project is unrelated to code splitting which is what --modules is referring to in this context. The ClojureScript GSoC project was about integrating the variety of JS module formats (CommonJS, AMD, ES2015) found in
94.
by swannodette 11y ago
It's not clear what you're referring to wrt. "the approach FB took with Flow" and Abstract Interpretation. Type checking? Dead code elimination? In anycase, Google Closure Compiler also leverages Abstract Interpretation.
95.
by swannodette 11y ago
Wrapping Java and JavaScript libraries is not idiomatic Clojure(Script), this is the whole point of having good interop.
96.
by swannodette 11y ago
Except you target and interop well with #1 and #2 :)
97.
by swannodette 11y ago
Module support is already in 1.7.28 however it requires a corresponding release of the Google Closure Compiler.
98.
by swannodette 11y ago
I do in fact enjoy sleeping immensely. As alluded to in the post while I tend to do a lot of "driving" - this release was the result of a broader effort by the growing Clojure & ClojureScript communities.
99.
by swannodette 11y ago
A non-trivial portion of Clojure (data structures, compiler) are written in Java. In ClojureScript these are written in Clojure or ClojureScript so there's really not as much to share as it would seem.
100.
by swannodette 11y ago
ClojureScript will always run on the JVM. It's just that from now on it will also always run on JavaScript.
101.
by swannodette 11y ago
Yes it very well could. It really is the same compiler - and the compiler generates Closure Compiler compatible JavaScript.
102.
by swannodette 11y ago
Over the years the language differences between Clojure & ClojureScript have more or less been erased beyond very host specific details like String methods, no multithreading, etc. Clojure 1.7.0 landed reader conditional which permits w
103.
by swannodette 11y ago
Some inaccuracies here about Om. There are no message channels. There are no functional zippers. Component local state and lifecycle are critical React integration points. Hierarchy organized data is not required - people have succeeded at
104.
by swannodette 11y ago
This is not entirely accurate, the ClojureScript compiler actually internally propagates type information for further optimization. And nothing precludes a Typed ClojureScript which feeds even more information to the compiler.
105.
by swannodette 11y ago
There's very little in the JavaScript world that can't be made to work with ClojureScript. That said it could be made easier and official support for CommonJS and RequireJS is underway thanks to Maria Neise's Google Summer of
106.
by swannodette 11y ago
ClojureScript applications start smaller than jQuery so I'm not really sure what you mean. If you're already using jQuery then ClojureScript applications are not large in comparison. As far as your experiences sounds like a lot of
107.
by swannodette 11y ago
Not really. Advanced optimizations doesn't matter for server-side JS whether Node.js or Nashorn.
108.
by swannodette 11y ago
Some inaccuracies here. ClojureScript does not have to be compiled by Google Closure. That pass is an optional one for production builds. There is no "bridging" when using the Closure Compiler with non-Closure compatible code. The
109.
by swannodette 11y ago
Just wanted to chime in and say this beautiful application was built with a pretty cool technology stack: ClojureScript, Om (ClojureScript bindings to React), Clojure and Datomic.
110.
by swannodette 11y ago
I only have the utmost respect for Scheme & Common Lisp. However the thread is about ClojureScript and neither Scheme nor Common Lisp have comparable mature compile-to-JavaScript technology that I'm aware of. Back in the day I was
111.
by swannodette 11y ago
If you've been serving jQuery (~30K gzipped) to mobile web applications, ClojureScript has always been a fine alternative. ClojureScript applications start at around 20K gzipped and go up from there.
112.
Clojure at a Real Estate Portal(pitheringabout.com)
10 points by swannodette 12y ago|1 comments
113.
Lisp implemented in under 1K of JavaScript(github.com)
108 points by swannodette 12y ago|16 comments
114.
by swannodette 12y ago
ClojureScript is just another part of a typical Clojure stack. Yes ClojureScript job opportunities that don't involve Clojure are far more rare.
115.
by swannodette 12y ago
Anything that isn't JavaScript is a rounding error. But that doesn't mean ClojureScript isn't viable: ~4000 Github stars, ~1200 subscribers to the mailing list, ~100 contributors, ~900 closed issues, ~170 daily lurkers on IRC
116.
by swannodette 12y ago
My debugging experience with Counterclockwise wasn't very positive. But admittedly the last time I tried was a very long time ago and things may have changed significantly.
117.
by swannodette 12y ago
Kyle's suggestions have a ton of value, but do note that debugging Clojure(Script) can also be a pedestrian activity if you so desire. All the usual mainstream bell/whistles IDE-based interactive debugging is available today in Cu
118.
by swannodette 12y ago
Well that code seems pretty readable to me and appears to preserve some interesting properties of the original paper as mentioned below the source :) As far as spending more time reading Clojure than writing it I experience this myself - an
119.
by swannodette 12y ago
That's not equivalent to inline protocol implementation in both Clojure or ClojureScript. The point still stands, the proposal runs afoul of macro composition issues. This isn't to pass judgement on the proposal, but this is a tra
120.
by swannodette 12y ago
I've seen plenty of Clojure core.async code that doesn't look like this at all. Also this discussion isn't considering the other reason for core.async's existence - ClojureScript - the patterns are completely different.

More ›