As an outcome of this thread, I have decided not to invest in clojure,
so I believe the following to be purely feedback, as I have no agenda
to push.
- it seems from some's point of view that I was trolling. Fine, from
my point of view though it was akin to drink the kool aid or gtfo.
Sorry,
As an outcome of this thread, I have decided not to invest in clojure,
so I believe the following to be purely feedback, as I have no agenda
to push.
- it seems from some's point of view that I was trolling. Fine, from
my point of view though it was akin to drink the kool aid or gtfo.
Sorry,
y I'am tThe main point for me of this whole discussion is that someone
should use clojurescript if he want to use clojure instead of javascript on
the browser.
Like GWT, JWT, ZK or other, you do not longer develop in the client
language. You develop in a different language and compile/generate
game for discussion
In principle the line is clear. Everything is fair game. Novel feedback is
always welcome. Question small decisions, question big ones. Press hard for
quality.
The opposite of providing novel feedback is recovering old ground. This takes
two (often overlapping) forms:
(1
On Sun, Jul 31, 2011 at 10:27 AM, Stuart Halloway
stuart.hallo...@gmail.com wrote:
In principle the line is clear. Everything is fair game. Novel feedback is
always welcome. Question small decisions, question big ones. Press hard for
quality.
The opposite of providing novel feedback
On Sun, Jul 31, 2011 at 10:41 AM, Ken Wesson kwess...@gmail.com wrote:
(I also have concerns about the *unchecked-math* flag I heard about
somewhere. We can't have +, etc. testing some flag at runtime -- much
less fetching a dynamic Var, which is a slow, slow ThreadLocal object
at the JVM
