Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ranting begins ...

    AFAICT, the author of the piece you linked is mostly reiterating arguments made by David Heinemeier Hansson, the Rails guy. This just confirms for me that Rails is not all that, particularly when it comes to an app with a "real" schema, where by "real" I mean complex, as in many tables and many relationships between the tables.

    You work on Bricolage, so you know what dealing with a real schema is like, but most people develop apps with relatively simple data, AFAICT. In those cases, simplistic ORM mapping layers like what's in Rails or what Maypole provides work fine. They save you tons of manual labor, and you think it's the shiznit. Then those people try to apply the same style to a more complex schema, and suddenly that layer is not helping much at all, because you still have to hand code all the hard parts.

    It's really scary to me that David won that Open Source Award for Rails, frankly. The vast majority of software developers don't understand data, AFAICT, which is worrying considering that our job generally centers around the manipulation, presentation, and storage of data!