Boss Ross has declared that we are far enough out of stealth mode for me to use my powers as Tucows’ TC/DC (Technical Community Development Coordinator) and actually say what language the developers are using to write this pretty cool blogging tool called Blogware…
Ruby!
Some of you might right now be cocking your head to one side. Ru-what? If you’re one of these people, Ruby is:
For more detailed information, check out the following:
Ruby is on the list of languages I’m actively learning, and I’ll be documenting my experiences and other Ruby-related news here.
I’m heading to Japan soon, and while researching places to go near Gotokuji, the temple…
It’s Sunday, and it’s time for another “picdump!” Here are the memes, pictures, and cartoons…
If you’re looking to get into the erotic waffle business on a limited budget, there’s…
Whoo-hoo! We managed to get a reservation to visit Yamaha’s Innovation Road museum in Hamamatsu,…
It’s Sunday, and it’s time for another “picdump,” but this is no ordinary picdump. This…
Is it just Florida, or do campaign ads for Governor in other states feel like…
View Comments
Dudical!! Ruby is out sekret weapon! ;-)
It should be noted that 1 is the only major difference from Python. I'm not sure whether it's a benefit or a liability.
- AaronSe
I've looked at Ruby a bunch of times. It is of course extremely similar to Python, to the extent that deciding between the two would be pretty much a coin-toss or aesthetic choice (some people are allergic to Python's indentation rules, others to Ruby's more Perl-like syntax) for most people. Since I already know Python, though, and in particular since I've gotten pretty damn good at writing extension modules for Python, I personally find insufficient reason to switch.
The metaprogramming/overloading actually strikes me as a liability. It's not useful all that often, but it does give alpha-geek-wannabes a way to obfuscate their code so it's hard for anyone else to maintain it. There's also a performance cost, because now every operation even on builtin types has to involve a complete method lookup. Lastly, the lack of multiple inheritance just bugs me. I don't use MI that much, and then generally only in a shallow non-joining mixin kind of way, but its absence in Ruby still seems like a shortcoming.
Jeff Darcy