Since you have some experience with older/legacy databases, how would Ruby/RoR stack up against Java/Tapestry in regard to legacy databases and multiple databases? Ruby and RoR in particular is appealing, but my applications must reliably support DB2/400 in addition to MySQL (and sometimes others). The RoR wiki on DB2 (not to mention the additional idiosynchrosies of DB2/400) basically says it doesn't work. Many of my internal applications would otherwise be well-suited to RoR, but I can't live without fast and reliable DB2 database support with legacy/broken schemas (composite keys, sometimes no primary key, etc.) and reliable connection pooling. Java/Tapestry/Hibernate always works, but I would love to throw RoR into the mix.
Shawn Quoting Erik Hatcher <[EMAIL PROTECTED]>: > > On Dec 12, 2005, at 9:08 AM, Leonardo Quijano Vincenzi wrote: > >> Compilation isn't the key though. Testing (not just unit testing) > > >> is. > > As I like to re-test my 300+ pages applications for a syntax error > > > after a refactoring. I can use my time better, you know. > > Ever hear of "continuous integration"?! ;) Commit your changes, > let the server run the tests while you reply to e-mails. > > > Of course, there are a lot of Javascript examples too, and that > > doesn't mean Javascript is maintainable or reliable > > There you go blaming the language again. Remember, it's the > programmers that create bugs, not the language. Language matters, a > > lot, don't get me wrong. One of the most fun jobs I've ever had was > > me coding in COBOL, I kid you not.... and lots of VMS DCL scripting > > which was loads of fun. The system was architected extremely well, > > including the development processes of revision control (it's built > > into the VMS file system. We had scripts around it to manage our > desired process of a REAL and TEST environment), issue tracking, > releases (making a tape to send to clients), billing, etc. I've > never experienced and environment where things ran as smoothly as it > > did there... in COBOL and DCL. > > Erik > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
