On 4/21/06, Tim Dysinger <[EMAIL PROTECTED]> wrote: > Theo blew something like a half-million dollars in support by > offending DARPA. He offends everyone. So does Marc.
Granted. I really wasn't holding them up as role-models, just noting that they had achieved some success in spite of their poor interpersonal skills. > Force of personality isn't "cool" in my book. It reminds me of when > I was in my 20's and thought I new everything. Which is now just > embarrassing to remember. > > The general sense I'm getting from you is that you like Ruby and > Rails because you perceive it as Punk Rock and anti-establishment - > which from reading DHH's posts is exactly why he likes it too. The <snark>...</snark> tags were intended to indicate that I was *mocking* DHH and the Rails buzz, not trying to hold it up as a good thing. I forget sometimes that "snarky" isn't yet universal English parlance. I don't have much tolerance for spoiled rock stars, whether in the music or software industries. Which is not to say that DHH and the Rails core team are necessarily spoiled *yet*, but the "fsck-you" attitude hints it could head that way... > Let me clue you guys in on the Java side - nobody uses J2EE who knows > how to be productive. We keep it light and simple, Test First, > Spring, Hibernate, Unit Tests, MVC, POM (maven: project object models > - read: convention), Hibernate - all light weight APIs and > methodologies. Sounds delightful, if a bit spread out amongst many projects and tools. > So if you were to lay J2EE with no libraries along side RoR, you'd > have a boost over Java. If you were to test yourself against a > seasoned light-weight Java dev who knew the right tools, you wouldn't > be so lucky. I've been out of Java web development for a few years, so I'm just going to yield on this one and assume you're right. The issues that always bothered me about Java web development are not really unique to Java, or even to compiled OO languages; I've seen plenty of Perl and Python (and even *gasp* Ruby) frameworks and applications which commit the same design atrocities (XML for *everything*, even when it's really code, super-deep class hierarchies, abstractions for things that don't need abstracting, etc.) Basically, I *agree* with you about the cultural side of the Rails phenomenon, and I hope you're able to find enough to like about Ruby to stick around. If you've worked with Python, you're obviously already comfortable with the lack of strong typing and strict interfaces, so Ruby shouldn't give you much trouble. -Lennon _______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
