Wednesday, October 26, 2005

First thoughts on Ruby...

Thank god blocks are back.

What the hell is up with all the special characters and weird syntaxes? Feels like C's question mark colon is coming back.
Why do people always think having multiple ways to do the same thing is a good idea?
Mixins are good because ...
Parser errors remind me of the LValue errors I used to get out of Microsoft C compiler.

Maybe static typing is good for code generation as it allows code completion and easier refactoring. (Did Ted really say that???)

Ruby on rails looks more like a steam train than a modern locomotive. Better than what we have, but not environmentally friendly.

Most importantly:

I've only used it for a couple of days. Ask me in a week.

3 Comments:

Anonymous Anonymous said...

What the hell is up with all the special characters and weird syntaxes?

You mean the '@'s and such? I prefer smalltalk's approach... scope is based on declaration context.

I don't see the big value of not having to declare vars... but I'm still relatively new to Ruby.

Feels like C's question mark colon is coming back.

Where did it go?

Mixins are good because ...

promote modularity? SRP? Allow context dependant extension (see rspec for an example).

Maybe static typing is good for code generation as it allows code completion and easier refactoring. (Did Ted really say that???)

Code Completion... sure.. that would be nice. But not worth static typing.

Refactoring... refactoring tools started out in smalltalk... sure static typing may make them easier to build... but so...

Ruby on rails looks more like a steam train than a modern locomotive. Better than what we have, but not environmentally friendly.

Steam trains didn't go as fast and so generally didn't create such disasters when something went wrong.

Most importantly:

I've only used it for a couple of days. Ask me in a week.


I've been at it part time for a couple months now. I'm sold... it's far superior to Java.. now if we just had some proper tools.

Dave

7:27 a.m.  
Anonymous Anonymous said...

in regard to code completion:

http://homepage.mac.com/keithray/blog/2005/10/26#MicrosoftMindRot

Something not mentioned in the linked piece, code completion is of no use when you are test driving code... or programming by intention... you are writing code that uses code that you haven't written yet.

Dave

8:00 a.m.  
Anonymous Anonymous said...

Resistance is futile.
Soon you will be a Rubyist. Soon...

:-)

-Jonathan

11:25 a.m.  

Post a Comment

<< Home