Ruby Isn't Fun Anymore
adam.blog.heroku.com
adam.blog.heroku.com
Python, on the other hand, is establishing itself as a serious tool for serious programmers. Python developers don't get calls from crazy teenagers and blog about it.
People like that are swimming in a pond, and they are holding such long discussions about the state of the water in the pond, that they don't notice the rivers, lakes and oceans around them.
I would still not bet any money on Ruby.
I know there is a lot of very serious people using Ruby (and Rails), but the community that builds businesses around the technology needs to deliver a message to the kids: that they should behave or their toys will be taken away.
Tell me what langauge you use so I can irrationally avoid it.
Feel free to avoid any language you want. The point I was making is that I have no energy to deal with childish behavior of toxic community leaders and their abandoned minions. Life is too short and my to-do list is way too long. :-)
I am not saying I will not use Ruby or Rails - it's a very nice stack. But, most certainly, I will not invest much time contributing to it unless the rest of the community sheds away its more toxic members.
What you can clearly see between the tenors of the two communities is that there is more surface-level drama in the Ruby community.
What that has to do with anything professional, I have no idea. I read Ruby blog posts and mailing list entries, but I don't write them; I write code (and here) instead.
Did people vote this thing up without reading it just because it's about Ruby or is there something particularly significant and worthwhile about this post?
The fact that the story gets voted up is a consequence of this, perhaps.
(Of course, there's still a long way to go until those criteria are satisfied, so I suppose it's still somewhat fun. Maybe not dance-around-naked-with-a-lampshade-on-your-head fun, but then, Zed's moved on...)
But if you got your fun from playing around with the language itself, exploring its nooks and crannies, and bring what you learned to other languages, there's no end to what fun you can have.
_why re-discovered adding and removing mixins from digging around the late Guy's archives, and implemented it as mixico http://hackety.org/2008/10/06/mixingOurWayOutOfInstanceEval....
And hell, this guy implemented fizzbuzz using C++ metaprogramming. http://web.telia.com/~u43518104/articles/fizzbuzz.htm
Just like the adage, "you can write bad code in any langauge", well, you can bore yourself to death in any language, as well. If you are doing boring things, your programming langauge choice isn't going to magically make something fun. (The opposite isn't true, though. If you pick Java or PHP for your project, you won't have much time for having fun.)
But don't worry, there will always be a new language for the fanbois to latch on to. This week, it's Clojure. (And for the record, I like Clojure. It's just hard to read anything about Lisp and not hear 138 Clojure fanbois talk about "OMG ITS THE JVM!!1", and that is pretty annoying. Blog posters should be required to install the language and write "hello world" before they start advocating it.)
But regardless, I think that ruby has a while before it loses steam. It's inherently a fun language
What I find fun about ruby is that, for better or worse, the language makes it convenient to express programs in a way that is very close to how I naturally think about them. Also: it's got pretty good libraries and a good community.
I would've found this blog post worth reading if the author would've explained why the shift from upstart to accepted technology means that for people like him ruby is no longer fun.