News for hackers. Stuff that matters.
Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by v_ignatyev on Monday December 29, 2014 @03:56PM (#8811719)
It's interesting. I love the idea. Some of code snippets can look larger. Look at the http://rosetta.alhur.es/compare/Java/Python/#Call_a_function for example. Java code has missed function definition (definition of class and method inside it) in comparison to Python code. It's unfair a bit! Not because I'm Python nerd :) But because of it too.

Additionally I would suggest to redirect user from http://rosetta.alhur.es/compare/ to http://rosetta.alhur.es/

Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by fiatjaf on Monday December 29, 2014 @04:09PM (#8811789)
The code snippets are from http://rosettacode.org/, I'm not responsible for the unfairness!

And thanks, I'm redirecting from http://rosetta.alhur.es/compare/ to http://rosetta.alhur.es/ now.

Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by adwhit on Sunday December 28, 2014 @02:56PM (#8807235)
Nice!

I made something very similar last year[0] but never really found the time to polish it to my satisfaction.

[0] http://www.rosettaclone.org/

Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by fiatjaf on Sunday December 28, 2014 @03:21PM (#8807312)
Wow, yours is great. If I had seem it I probably wouldn't try to write my own.

One problem we are facing (me, you, rosettacode.org itself) is that is difficult to find the examples that will help you more at any given time (but definitely my solution -- show everything randomly -- is the worse).

Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by bsou on Sunday December 28, 2014 @02:53PM (#8807220)
love the idea, though i'm getting 404ed when I try to compare haskell and coffeescript (osx / opera 26) http://rosetta.alhur.es/compare/Coffeescript/Haskell/#
Re:Show HN: Usable RosettaCode: Code snippets for 2 language... by fiatjaf on Sunday December 28, 2014 @03:19PM (#8807306)
Right, I think part of this is due to the slash (/) in the names of the tasks, but there's a bigger issue somewhere.