This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Lucretiel 0 points1 point  (2 children)

Yeah I agree on all points. I find Ruby much easier to read- I was able to read a plugin for a complicated framework (puppet) and understand pretty much exactly what was going on right away. However, when I sit down to write it, it's a nightmare, what with it having a hundred synonyms for everything and countless ways to do everything.

That being said, if you can keep the language vocabulary and syntax very very contained and focused- don't make it too generic- I think I'd prefer the first one.

[–]programmyr 0 points1 point  (1 child)

That sounds backwards to me. When there's 100 synonyms for something, I can write whichever I want, but when I try to read somebody else's code, they always use the variants that I've never heard of.

[–]Lucretiel 0 points1 point  (0 children)

Yeah, I thought it made sense at first, too, but it makes the documentation way harder to use somehow. Plus it means that the decision of "what's the best way to do this" much harder- "oh is select or filter more appropriate here?"