That's why you won't hear the words "components" and "configurable" too often in the Rails community. It's often much faster to write your own customized stuff instead of trying to configure a prefab component-- because of the speed you can develop with a dynamic language. :) Embedding defensive techniques is good of course, and your unit tests should include throwing strange stuff at your code. Nevertheless, static typing isn't a catch-all and could even lead to a false sense of security. The problem is that you easily get to the point that you try to "force" the language into something that it just isn't-- Microsoft tried something like that with their "Atlas" framework (Java-style OO), and IMHO miserably failed. Anyway, this has already been discussed to death (maybe check the rails mailing list archives), and neither way of doing things is the holy grail, plus it depends heavily on personal experience and preference, how things work in the team, maybe corporate policies, phase of the moon, etc. etc. Best, -Thomas Am 31.07.2006 um 15:42 schrieb Ryan Gahl: However, when creating consumable components or APIs, it's always good to embed defensive techniques into your code because you may not know which anonymous application space is trying to do what with your stuff, and yes you can tell those 3rd parties to unit test unit test, but in the end you can't control that. -- Thomas Fuchs wollzelle questentier on AIM madrobby on irc.freenode.net http://www.fluxiom.com :: online digital asset management http://script.aculo.us :: Web 2.0 _javascript_ http://mir.aculo.us :: Where no web developer has gone before |
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
