Live data from Hacker News

Introducing Closure Tools

googlecode.blogspot.com

11–20 of 71 posts

Re: Introducing Closure Tools

#12

Earlier quoted context omitted.

It was called Closure before Rich announced Clojure to the world.

"Closure" being a general concept in programming, I always disliked the name "Clojure". Same thing as Google Chrome, everyone is now confused when you talk about browser chrome as a general thing.

Naming is a pretty powerful thing. If you name your crap with regular nouns, what's left for others there?

Like, suppose you build a crappy GUI system and just dub everything based on simple self-describing words such as windows, word, notepad, internet explorer, you might end up wildly successful yet for reasons other than technical superiority.

Re: Introducing Closure Tools

#14

So now there is Clozure common lisp, Clojure for the JVM, and now Closure. I was already getting the first two mixed up.

Upvoted for two reasons - Making me laugh out loud, and for letting me know that I am not the only one getting confused.

Other commentators have mentioned the confusion with Rich's Clojure, and despite Rich's stand that is be pronounced like you would pronounce "closure", I usually still say it with the emphasis on the "J", esp. to Lisp-savvy folks.

[On a side note, and I am nitpicking here, but it's just Clojure, vs Clojure for the JVM, considering Clojure for the CLR is very close to 1.0]

Re: Introducing Closure Tools

#15
post #2

What an unfortunate name. Perhaps, in the confusion, it will help to actually promote Rich Hickey's wonderful work.

Despite the closeness in name, aren't they pronounced differently? I've always pronounced "Clojure" with a hard "j," rather than like "closure."

Edit: Turns out soft "j" is order of the day, there's a whole discussion about it: http://groups.google.com/group/clojure/browse_thread/thread/... - so confusion can continue to reign ;-)

Re: Introducing Closure Tools

#16

Earlier quoted context omitted.

It was called Closure before Rich announced Clojure to the world.

"Closure" being a general concept in programming, I always disliked the name "Clojure". Same thing as Google Chrome, everyone is now confused when you talk about browser chrome as a general thing.

I agree that "Clojure" is kinda a silly name, but what else are you gonna call it? I assume Henly wanted a name that conveyed its functional and/or Lisp roots, and the fact that it's on the JVM.

Let's try some names using the usual JVM language conventions: JLisp works, but it's boring, and Jisp sounds kinda suspect. Parenjases is just silly. Or maybe LLBeans for "lazy lisp beans"...but that's just getting too cute.

I think I probably would have gone with Jambda.

Re: Introducing Closure Tools

#17
Would anyone who already knows this tool, or is taking the time to learn it, care to explain what they mean by "compiles web apps down into compact, high-performance JavaScript"? I assume this is a JS-to-JS translator. How exactly are they transforming the JS?

I mean, of course, besides the obvious things they mention: minification, removing dead code, and some error checking.

Re: Introducing Closure Tools

#19
post #2

What an unfortunate name. Perhaps, in the confusion, it will help to actually promote Rich Hickey's wonderful work.

It was called Closure before Rich announced Clojure to the world.

Thats a terrible argument... He did indeed "announce Clojure to the world" before Google did, and now we all associate the phonetic name with him. Treat "closure" as a project name and pick a different product name, Google.

Re: Introducing Closure Tools

#20
I've been curious about some of the tools behind Google's javascript power. The Closure Library coupled with the compiler looks really useful for creating complex and fast web apps.
Post reply on HN