News for hackers. Stuff that matters.
Re:Why we are choosing Clojure as our main programming language by icey on Monday March 21, 2011 @01:20PM (#2350631)
F# runs on mono, which runs pretty well everywhere Clojure will run.

The F# mono implementation is somewhat slower than the .Net implementation though, so there is that caveat.

Re:Why we are choosing Clojure as our main programming language by mduerksen on Monday March 21, 2011 @02:55PM (#2351083)
Clojure can utilize all libraries available for Java, and all invocations of those libraries will have the exact same speed any java application would have (Clojure itself isn't slow either, but that's a different topic).

I never attemped to actually use Mono, so please correct me if I'm wrong, but if I understood correctly, Mono has to duplicate all .NET frameworks, libraries and tools, which means Mono

a) is not complete (e.g. Silverlight, VisualStudio)

b) will hardly ever keep the pace of development of Microsofts implementation (simply due to resources).

Mono may be viable if you are happy with a subset of the .NET ecosystem, but I'd really feel more comfortable if I have access to all of Java with Clojure. Chances are you do need that library...

Re:Why we are choosing Clojure as our main programming language by icey on Monday March 21, 2011 @10:54PM (#2352842)
Mono can utilize all the libraries available for .Net, with a few exceptions (which are well known and documented on Mono's site here: http://www.mono-project.com/Compatibility).

Mono is a complete implementation of the C# specification, additionally, the Mono project has ported many .Net libraries.

Moonlight is the Mono version of Silverlight. Visual Studio is an IDE, and doesn't have anything to do with Mono vs .Net (in the same way IntelliJ IDEA has nothing to do with Java portability). You can write code in Visual Studio and compile it with Mono with no problems. You can also use MonoDevelop on OSX and Linux.

The time between Microsoft releasing new versions of .Net / C# and the Mono implementation is very small, usually weeks but sometimes only days. Unless you need to work on the bleeding edge right now, I don't think that it really makes much of a difference.

Yes, you can write C# in a way that isn't portable, especially if you use libraries that are OS specific. You can do that in Java as well (or any other language). Just look at all the libraries that require epoll or kqueue - those won't run on Windows no matter what language they were written in.

It's unfair to say that Mono requires you use a subset of the .Net ecosystem. If you want to write cross-platform code, you will always be constrained to a subset of the libraries.

C# is a nice language, especially with Linq (which is in Mono). You should spend a weekend with it sometime to form an opinion :D. MonoDevelop works fine on the mac and is free.

Re:Why we are choosing Clojure as our main programming language by seanx on Tuesday March 22, 2011 @08:03PM (#2357187)
Also, some recent MS libraries for .net are released as open source (e.g. MVC) and consequently work just fine on Mono when released.
Re:Why we are choosing Clojure as our main programming language by Turing_Machine on Monday March 21, 2011 @01:31PM (#2350681)
F# on Mono seems to be a lot slower than Java 6, at least in the Shootout (2x to 12x). I don't know how that stacks up to Clojure, though I understand that Clojure can be much more performant with tricks like type hinting.

On the other hand, F# does use less memory.

http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...

Re:Why we are choosing Clojure as our main programming language by icey on Monday March 21, 2011 @01:35PM (#2350699)
I really dislike the shootout, but F# on mono and Clojure (which is slower than plain Java) look pretty similar:

http://shootout.alioth.debian.org/u32/benchmark.php?test=all...

For whatever it's worth, if you like Clojure, use Clojure. If you like F# use that. If you like Perl, Java, PHP, use those. But, if you're going to consider other options hopefully the FUD doesn't get in the way ;).

Re:Why we are choosing Clojure as our main programming language by igouy on Monday March 21, 2011 @05:46PM (#2351759)
If you really dislike the benchmarks game, don't look at the benchmarks game and don't show it to other people :-)
Re:Why we are choosing Clojure as our main programming language by gtani on Tuesday March 22, 2011 @11:33AM (#2354825)
OK, igouy, somebody has to defend the Benchmarks game (!?)

Most FP communities (incl clojure) have devote non-negligible blocks of time to code review and benchmarking to make sure that at the very least poorly written code isnt' submitted (and the right hotspot knobs are on).

http://groups.google.com/group/clojure/browse_frm/thread/d27...

Re:Why we are choosing Clojure as our main programming language by igouy on Tuesday March 22, 2011 @02:05PM (#2355544)
Let's ignore your guesses about "most FP communities" and look at your example -

iirc Andy Fingerhut started benchmarking Clojure programs more than a year before Clojure was even included in the benchmarks game.

https://github.com/jafingerhut/clojure-benchmarks

Here's another thread "Comparing clojure speed to java speed" which has nothing what-so-ever to do with the benchmarks game -

http://groups.google.com/group/clojure/browse_thread/thread/...

(Incidentally, those "hotspot knobs" made the Clojure programs slightly slower but forced collection of the temporary objects that were showing up as much greater memory use than the Java programs.)

Re:Why we are choosing Clojure as our main programming language by igouy on Tuesday March 22, 2011 @01:14PM (#2355294)
I did not "defend the Benchmarks game".

I pointed out how comical it is for someone to declare they dislike (who knows why?) the benchmarks game, and then present the benchmarks game to others as a reliable source of information.

Re:Why we are choosing Clojure as our main programming language by icey on Tuesday March 22, 2011 @04:54PM (#2356435)
I didn't present it as a reliable anything. I pointed out that the parent had linked to the wrong comparison, and linked to the correct one.
Re:Why we are choosing Clojure as our main programming language by igouy on Tuesday March 22, 2011 @05:25PM (#2356583)
I'm happy to be corrected about what you intended us to understand by your comment.

(However, although you provided a different URL you did not point out that you thought the parent had linked to the wrong comparison.)

Re:Why we are choosing Clojure as our main programming language by icey on Tuesday March 22, 2011 @05:27PM (#2356588)
I thought placing emphasis on the correct one was enough; evidently I was mistaken.
Re:Why we are choosing Clojure as our main programming language by igouy on Tuesday March 22, 2011 @07:38PM (#2357112)
The parent was correct about what their link showed - "F# on Mono seems to be a lot slower than Java 6".

You didn't just "correct" the link to show F# and Clojure.

You changed the link from quad-core to single core and that reduced the difference shown between F# on Mono and Clojure.

Re:Why we are choosing Clojure as our main programming language by icey on Tuesday March 22, 2011 @08:00PM (#2357174)
Come on dude, is it that hard to change the dropdown yourself??? The parent was talking about CLOJURE and linked to JAVA's RESULTS

Look, the results aren't usefully different: http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...

Re:Why we are choosing Clojure as our main programming language by igouy on Wednesday March 23, 2011 @10:20AM (#2359456)
You can easily get from the quad-core Java:F# to quad-core Clojure:F# by changing a drop-down but that isn't what you did.

You do seem to be using the what you dislike and what you are not presenting as reliable to suggest "F# on mono and Clojure (which is slower than plain Java) look pretty similar".

If you really dislike the benchmarks game, don't look at the benchmarks game and don't show it to other people :-)