Part 2 of my Rails article on ONLamp.com just made the slashdot front page! The entry, itself, is here: http://developers.slashdot.org/article.pl?sid=05/03/04/1319242&tid=156 Curt
On Fri, 4 Mar 2005 23:54:09 +0900, Curt Hibbs <curt-fk6st7iWb8MAvxtiuMwx3w@public.gmane.org> wrote:> Part 2 of my Rails article on ONLamp.com just made the slashdot front page! > The entry, itself, is here: > > http://developers.slashdot.org/article.pl?sid=05/03/04/1319242&tid=156 >Congrats! And thanks for all your work! Ran through your first article just yesterday, it was incredibly helpful. The timing of this one couldn''t be better for me :) -- Bill Guindon (aka aGorilla)
> > Part 2 of my Rails article on ONLamp.com just made the slashdot front page! > > The entry, itself, is here: > > > > http://developers.slashdot.org/article.pl?sid=05/03/04/1319242&tid=156 > >Check out this Slashdot comment: ------------------------- "It''s a collection of Java Best Practices rewritten in a ''cool'' geeky language. Nothing new...." Quite true. For example, Java Best Practice #1 is to avoid using long, detailed XML files for configuration, and instead use the programming languge itself, which is dynamically loaded and interpreted when needed. Another Java Best Practice is to let the framework write the tedious boilerplate code for you. For example, in Struts, you just run % struts myAppName and you''re halfway done writing your Web application. Here''s one more Java Best Practice: Avoid expensive , complex application server software, and do rapid development using the Web server that is built into the standard library. Then deploy to the Web server of choice with no code changes or quirky vendor-specific API hacks. ------------------------- -- rick http://techno-weenie.net
Hi, On Fri, 4 Mar 2005 10:19:17 -0600, Rick Olson <technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > Part 2 of my Rails article on ONLamp.com just made the slashdot front page! > > > The entry, itself, is here: > > > > > > http://developers.slashdot.org/article.pl?sid=05/03/04/1319242&tid=156 > > > > > Check out this Slashdot comment: > ------------------------- > "It''s a collection of Java Best Practices rewritten in a ''cool'' geeky > language. Nothing new...." > > Quite true. For example, Java Best Practice #1 is to avoid using long, > detailed XML files for configuration, and instead use the programming > languge itself, which is dynamically loaded and interpreted when > needed. > > Another Java Best Practice is to let the framework write the tedious > boilerplate code for you. For example, in Struts, you just run > > % struts myAppName > > and you''re halfway done writing your Web application. > > Here''s one more Java Best Practice: Avoid expensive , complex > application server software, and do rapid development using the Web > server that is built into the standard library. Then deploy to the Web > server of choice with no code changes or quirky vendor-specific API > hacks. > -------------------------Check out this comment by Bruce Tate then: http://weblogs.java.net/blog/batate/archive/2005/02/the_toy_1.html Cheers, Joao