11–20 of 43 posts
Earlier quoted context omitted.
... and an example of web development in Clojure: http://mmcgrana.github.com/2010/03/clojure-web-development-r... Just install leiningen, whip out your favorite text editor, and you don't have to worry about downloading/installing clojure, libraries and deps.
... provided you have java installed.
Earlier quoted context omitted.
... provided you have java installed.
... which is likely if you use an Apple laptop and trivial if you don't
I wouldn't mind contributing to some official getting started documentation if that was possible. Seeing an HN comment as the go-to source for getting started upthread disappointed me.
Earlier quoted context omitted.
... which is likely if you use an Apple laptop and trivial if you don't
When I first started out with Clojure on Ubuntu I honestly had no idea which packages to start out with. It's not a huge deal and I was able to get it right through trial and error but it's one more step where a potential user could get lost. I wouldn't mind contributing to some official getting started documentation if that was possible. Seeing an HN comment as the go-to source for getting started upthread disappoin…
In the middle of the article, the author talks about three advantages that clojure has over ruby. Simply put, speed, easy concurrence and functional. I don't find these to be really good advantages.. First, "functional" isn't an advantage.. I mean, the advantage of functional code might be easier maintenance, concise code, easier to concurrence etc.. but "functional" isn't an advantage. It's like saying C++ is better…
> First, "functional" isn't an advantage.. I mean, the advantage of functional code might be easier maintenance, concise code, easier to concurrence etc.. Those are all good reasons why functional programming is an advantage. I guess you object to my grouping of all these under the "functional" umbrella term. > In my opinion, the advantage of clojure by comparing it with Ruby are: - You get the best of Java (lots of…
Clojure Dude (talking to ruby dude): Hey, you should try clojure.
Ruby Dude: What is clojure ?
Clojure Dude: Oh, clojure is a lisp/functional language. You should really give it a try.
Ruby Dude: Why?
Clojure Dude: Its main advantage is that it's functional.
Ruby Dude: Wow, you convince me. I'm switching!
Earlier quoted context omitted.
I don't think you should claim "demonstrable" and "future" in the same sentence. "Theoretical" or even "promising", perhaps. The most performance intensive problems in the world, when they have competition, are very much still solved in C and C++.
You're quite right about the juxtaposition of "demonstrable" and "future". I should have said functional programming has "already" demonstrated an advantage in producing robust and understandable concurrent programs, which will continue to be relevant in our multicore future. Really, there's nothing "theoretical" about that fact. To your second point, I made no claims that C and C++ are not used to solve performance…
Examples of this other than Erlang?
In the middle of the article, the author talks about three advantages that clojure has over ruby. Simply put, speed, easy concurrence and functional. I don't find these to be really good advantages.. First, "functional" isn't an advantage.. I mean, the advantage of functional code might be easier maintenance, concise code, easier to concurrence etc.. but "functional" isn't an advantage. It's like saying C++ is better…
For a certain (large) class of programs, being "functional" is an advantage. Interestingly, you made the point that being functional means easier maintenance etc., but fail to attribute those advantages to being functional. If your argument is that there can be bad functional code which performs worse than non-functional (imperative or OO) code, I don't disagree. However, in the multicore future that our semiconducto…
http://www.infoq.com/interviews/armstrong-peyton-jones-erlan...
But it turned out to be very hard to turn that into actual wall clock speedups on processes, leaving aside all issues of robustness or that kind of stuff, because if you do that style of concurrency you get lots of very tiny fine-grained processes and you get no locality and you get very difficult scheduling problems. The overheads overwhelm the benefits, in short.
It may be true that FP does make concurrency easier, but I don't think this has been demonstrated to be generally true yet and it's certainly not as simple as just eliminating side effects from your code.
Earlier quoted context omitted.
... which is likely if you use an Apple laptop and trivial if you don't
When I first started out with Clojure on Ubuntu I honestly had no idea which packages to start out with. It's not a huge deal and I was able to get it right through trial and error but it's one more step where a potential user could get lost. I wouldn't mind contributing to some official getting started documentation if that was possible. Seeing an HN comment as the go-to source for getting started upthread disappoin…
What you're asking wasn't the intended scope of my comment, but it is covered by the 4th item: http://en.wikibooks.org/wiki/Clojure_Programming, specifically: http://en.wikibooks.org/wiki/Clojure_Programming/Getting_Sta...
To a great extent the previous items are intended to convince you to give Clojure a try/orient you before you start typing in a REPL.
Learning a functional language is not necessarily hard but many people say it's harder than programmers who are experienced in imperative programming expect. The latter are used to picking up new imperative languages and the change to the functional paradigm is not as easy. On the other hand, the more scars they have from side effect induced bugs the more they appreciate it.
I really want to get into Clojure, but everything I've read suggests that I'll have to learn Emacs to do it. Does anyone think giving up Vim for a few months is worth it?