×
The Ruby and Rails community linklog
Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!
Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!
Comments
Either this person doesn’t really understand ruby or just wants to attack the language. Not really worth the read.
You know, lifo is actually a core contributor to rails. I don’t think it’s the case that he doesn’t understand ruby, and I don’t think he’s necessarily attacking the language design itself. I’ve never been a fan on him, though, because he sounds snippy in a lot of lighthouse tickets. But I think that might just be pure personal reasons, and has nothing to do with his competency.
@WesInCa I hope you have some real arguments and not just ad hominem stupidity !
@Brendan - Umm..thanks! Sorry if I’ve sounded snippy on your tickets. LH is usually a mess - too many tickets and not enough people to care for them. So when I work on cleaning up LH, I just aim to work on as many tickets as possible, which indirectly makes it sound like I’m being rude. But everything is open to discussion in the Rails core mailing list.
Kind of an odd whine-fest. Explicit return is pretty much a cosmetic choice, though I generally favor implicit return as well as single point of return. Throw/catch has its place and I’m glad the language supports it, though it’s rarely used in practice, so I’m not sure why he’s singled it out. Object#freeze has its place. I’ve used it on occasion when reporting data structures returning operating system information that’s strictly read-only, e.g. no, you cannot set your CPU speed, I’m merely reporting it to you. :)
Post a comment