4 ms·
Yeah. The condition of rubygems are generally so bad (unfinished and/or abandoned), that I would strongly recommend Python over Ruby for new projects - which is
by jes5199 13y ago
Yeah. The condition of rubygems are generally so bad (unfinished and/or abandoned), that I would strongly recommend Python over Ruby for new projects - which is a shame, in the core language Ruby is more elegant and more fun to write, and I know Ruby much better than I know Python. (for a concrete example, compare "NumPy" to the various attempts at good math structures in ruby)
I wish I could recommend perl - CPAN modules generally really are amazingly high quality. But the mental cost of the perl programming model: no named params! arrayref vs array vs list! Contextual::Return! blessing scalars into objects! - that cost is just so friggin high that I can't imagine asking anyone to follow me there anymore.
- berntb 13y agoReferences do suck. All languages have ugly misfeatures, by nature. (Some language groupie collectives are in denial...) But you get named parameters (and type checking of them!) for functions/methods through CPAN. And lots of other language extensions. High flexibility in programming languages -- Perl isn't close to e.g. Lisp macros -- do have costs, of course. You need to use automatic tools, code reviews and coding standards. But you should do that anyway. I really doubt the extra time/cognitive costs make for a noticeable extra burden, considering that you'll have to learn lots and lots of other stuff anyway.
- Mithaldu 13y agoYou may find that stuff is quite easy to learn when taught by a good teacher. Try giving chromatic's Modern Perl a read sometime.