Re: Clojure analysis

2009-12-18 Thread Santhosh G R
> Lookup (and contrast) words "analysis" and "opinion" in your favorite > dictionary. Being a blog I thought that analysis would be from my perspective and hence an opinion. Dictionaries become muddied in the blog world, and mea culpa. If nothing else, at least I will make sure that I am careful :

Re: Clojure analysis

2009-12-18 Thread Martin Coxall
On 18 Dec 2009, at 06:42, Mike Meyer wrote: > On Fri, 18 Dec 2009 00:44:02 -0500 > Luc Préfontaine wrote: > >> Mike, I think that the whole issue about Lisp creates a big cloud >> about >> Clojure. > > Yes, it does. When I mention that, people tend to shudder. That's the price Clojure pays

Re: Clojure analysis

2009-12-18 Thread Mike Meyer
On Fri, 18 Dec 2009 00:44:02 -0500 Luc Préfontaine wrote: > Mike, I think that the whole issue about Lisp creates a big cloud about > Clojure. Yes, it does. When I mention that, people tend to shudder. > If you sum up Clojure as being a Lisp because of what it look likes and > use only this to

Re: Clojure analysis

2009-12-17 Thread Dmitry Kakurin
On Dec 17, 10:42 am, Santhosh G R wrote: > Again the same statement about being humble :-( The "humble" comment relates to the title of your article. Lookup (and contrast) words "analysis" and "opinion" in your favorite dictionary. Were your post named "My opinion about Clojure" I would not make

Re: Clojure analysis

2009-12-17 Thread Luc Préfontaine
Mike, I think that the whole issue about Lisp creates a big cloud about Clojure. Choosing a Lisp like syntax for a new language is a good choice because of the expressiveness, it requires less code lines, yields a better design, easier to test, ... That's a choice between a number of options. If i

Re: Clojure analysis

2009-12-17 Thread Eric Lavigne
I was still using 1.0. This is a good incentive to upgrade :-) On Fri, Dec 18, 2009 at 12:22 AM, Sean Devlin wrote: > It's new in 1.1.  Go here: > > http://clojure.org/special_forms#toc7 > > And read the "Since 1.1" section. > > On Dec 17, 11:58 pm, Eric Lavigne wrote: >> > Given that list of la

Re: Clojure analysis

2009-12-17 Thread Sean Devlin
It's new in 1.1. Go here: http://clojure.org/special_forms#toc7 And read the "Since 1.1" section. On Dec 17, 11:58 pm, Eric Lavigne wrote: > > Given that list of languages, I'd suggest taking a look at Eiffel. > > ... > > It's the source of the function pre/post condition facilities that Cloju

Re: Clojure analysis

2009-12-17 Thread Eric Lavigne
> Given that list of languages, I'd suggest taking a look at Eiffel. > ... > It's the source of the function pre/post condition facilities that Clojure > has. I did not know that Clojure functions supported Eiffel-style pre/post conditions. Where can I read more about this? -- You received this

Re: Clojure analysis

2009-12-17 Thread Mike Meyer
On Thu, 17 Dec 2009 10:26:03 -0800 (PST) Santhosh G R wrote: > > You warn that you learn languages "just for the fun of it". I would be > > curious to know how much time you spent learning Clojure... > > I have been working with Scheme for the past 5 years. I think this is a critical element!

Re: Clojure analysis

2009-12-17 Thread ajay gopalakrishnan
I was about to point out this reference, but realized Rich has already already given a nice explanation. Good to know that this newbie (myself) is on the right track! On Thu, Dec 17, 2009 at 3:24 PM, Rich Hickey wrote: > > > On Dec 17, 2:16 pm, Martin Coxall wrote: > > On 17 Dec 2009, at 10:04,

Re: Clojure analysis

2009-12-17 Thread Alex Osborne
Santhosh G R writes: >> > Clojure is a multi-paradigm language >> no it's not, and it's most certainty not an OOP >> language:http://clojure.org/rationale > > I hear about this everywhere. Is Clojure not a multi-paradigm language > because that is the rationale for the language? For me - It supp

Re: Clojure analysis

2009-12-17 Thread Rich Hickey
On Dec 17, 2:16 pm, Martin Coxall wrote: > On 17 Dec 2009, at 10:04, Dmitry Kakurin wrote: > > > Please keep in mind that it is almost literally the speech that I give > > to my friends/colleagues when they ask me why am I so excited about > > Clojure. I did it many times now and I have quickly

Re: Clojure analysis

2009-12-17 Thread Martin Coxall
On 17 Dec 2009, at 10:04, Dmitry Kakurin wrote: > Please keep in mind that it is almost literally the speech that I give > to my friends/colleagues when they ask me why am I so excited about > Clojure. I did it many times now and I have quickly learned that > saying "persistent data structures" g

Re: Clojure analysis

2009-12-17 Thread Santhosh G R
Thanks Dmitry and Richard. In all the replies I found yours to be the most "humble". Even though my analysis says otherwise, I am doing the elevator pitch for Clojure wherever I work. Of course, in an enterprise (where I work), nobody is going to buy it; but in my own world I use Clojure more than

Re: Clojure analysis

2009-12-17 Thread Santhosh G R
> Judging by the article you've spent very little time "learning" > Clojure and have managed to get every key point wrong: > > Clojure is a multi-paradigm language > no it's not, and it's most certainty not an OOP > language:http://clojure.org/rationale I hear about this everywhere. Is Clojure no

Re: Clojure analysis

2009-12-17 Thread Santhosh G R
> You warn that you learn languages "just for the fun of it". I would be > curious to know how much time you spent learning Clojure... I have been working with Scheme for the past 5 years. Yep, I don't have 20+ years in development; neither 12+ months in Clojure. My learning of Clojure has been fo

Re: Clojure analysis

2009-12-17 Thread Laurent PETIT
That's quite true ! 2009/12/17 Dmitry Kakurin > Please keep in mind that it is almost literally the speech that I give > to my friends/colleagues when they ask me why am I so excited about > Clojure. I did it many times now and I have quickly learned that > saying "persistent data structures" ge

Re: Clojure analysis

2009-12-17 Thread Dmitry Kakurin
Please keep in mind that it is almost literally the speech that I give to my friends/colleagues when they ask me why am I so excited about Clojure. I did it many times now and I have quickly learned that saying "persistent data structures" gets misinterpreted by every single person as "something yo

Re: Clojure analysis

2009-12-17 Thread Laurent PETIT
Thanks Richard for the good link. So to be even more precise, we can say that clojure's data structures are "fully" persistent since any older version of the datastructure can still serve as the basis to create new versions. 2009/12/17 Richard Newman > > I just learned (the hard way, by being h

Re: Clojure analysis

2009-12-17 Thread Richard Newman
> I just learned (the hard way, by being humble and asking :-) ) on > #clojure that one does not say "immutable" collections but > "persistent" collections, since "persistent" conveys a lot more > information about what Rich has achieved than just saying "immutable". Good explanation: http:

Re: Clojure analysis

2009-12-17 Thread Laurent PETIT
Hello, 2009/12/17 Dmitry Kakurin > Judging by the article you've spent very little time "learning" > Clojure and have managed to get every key point wrong: > > > Clojure is a multi-paradigm language > > no it's not, and it's most certainty not an OOP language: > http://clojure.org/rationale > >

Re: Clojure analysis

2009-12-16 Thread Dmitry Kakurin
Judging by the article you've spent very little time "learning" Clojure and have managed to get every key point wrong: > Clojure is a multi-paradigm language no it's not, and it's most certainty not an OOP language: http://clojure.org/rationale > Functional programming finds its best implementat

Re: Clojure analysis

2009-12-16 Thread Luc Préfontaine
I agree with Sean, the STM is a big feature also are parallelism and data immutability. These features are working now and they make things a lot simpler. I agree also that the lack of documentation is a barrier but even with documentation the learning curve would not be much shorter again becaus

Re: Clojure analysis

2009-12-12 Thread Joseph Smith
I think referring to clojure as a multiparadigm languge is incorrect. --- Joseph Smith j...@uwcreations.com (402)601-5443 On Dec 11, 2009, at 3:04 PM, kusi wrote: > http://kusimari.blogspot.com/2009/12/analysing-clojure-programming-language.html > > -- > You received this message because you

Re: Clojure analysis

2009-12-12 Thread Joost
On 12 dec, 17:29, Sean Devlin wrote: > First, is the STM.  This is THE killer feature of the language. > Ironically, it gives Clojure its identity, and ridiculously clean > design.  Write a concurrent app with it and you'll see. For me, it's not even the STM that's so compelling about clojure - i

Re: Clojure analysis

2009-12-12 Thread Stuart Halloway
The linked article is poorly researched and incorrect starting at the very first sentence. I hope that the author will have time to do a more in-depth exploration of Clojure and make some modifications. If you are looking for accurate introductory information on Clojure, I would recommend:

Re: Clojure analysis

2009-12-12 Thread Sean Devlin
I'm guessing you're the author. A very interesting critique. Well written, and you've got guts posting it to this list. There are a few very important factors you need to consider to have a complete critique, though. First, is the STM. This is THE killer feature of the language. Ironically, it

Clojure analysis

2009-12-12 Thread kusi
http://kusimari.blogspot.com/2009/12/analysing-clojure-programming-language.html -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be p