Thanks for digging up this article. Anyone reading it, be sure to check the slides. They represent the core of the Ruby thought and will tell you exactly why R

Thanks for digging up this article. Anyone reading it, be sure to check the slides. They represent the core of the Ruby thought and will tell you exactly why Ruby was so successful. To me it is not just a list of design principles, but it's also a Manifesto - whose points I've seen to be proven true in practice - for how programming should be in general. "Coders should be happy. Simple things should be simple, non simple things should be possible. Code should be easy to infer with common sense, both when reading and writing it. This will increase your productivity and leave you with a smart, happy feeling." Too bad, from time to time, some human devs mentally enslaved to machines (been there.. it might not be entirely our fault.. ) will drag other devs in some sort of sick competition where they keep telling that there's one big thing worth the sacrifice of all those healthy principles above: speed of execution. And here we go, exactly back to teenage who's got-it-longer times. So sad. And also, who's going to benefit when two slaves compete for speed of execution? This seems a simple concept but it is struggling to become accepted. It meets a lot of resistance, exactly like how organic food was meeting at the beginning. Realizing that you are hurting yourself, hurts so much that one does not want to see it. Ruby proved that programming CAN be healthy (as in fun and productive at the same time). Now it's our duty to say that it MUST be so before everything else. Does that mean that a couple of $M less for big companies HQ's? Oh well..