On Fri, 28 Jan 2005, Joao Pedrosa wrote:

> 2- Try to not think about interfaces, but enjoy fully the dynamic typing.

*Think* about interfaces, but for yourself, not for the compiler's
benefit. Don't *worry* about interface. Still enjoy fully the dynamic
typing.

> 5- Don't worry about performance until the program/library has been made.

In any language, I'd say, think about global performance issues before
writing the program (or at every major refactoring), but don't worry about
local performance issues until everything works. When one says "premature
optimisation is the root of all evil" it's usually implied that it's about
local optimisations.

> 10- Ruby is not a Silver Bullet, unlike Java, right? :-)

Java's marketing/gospel/selfcontradiction/bellythinking department has
caused a lot of harm, so when looking at which preconceptions to drop
first, start there!

11- Reflection in Ruby is much easier than in Java, and more deeply into
the language than the java.lang.reflect tack-on.

12- eval.

13- the builtin classes are much faster because they're written in C and
not Ruby, and this should be taken into account. (same as for
Perl/Python/Tcl/...)

_____________________________________________________________________
Mathieu Bouchard -=- MontrñÂl QC Canada -=- http://artengine.ca/matju