It sounds like you're complaining about the way the different pieces are named. Who cares? You're right that the way Smalltalk defines things is not the same as most web versions do it, but that doesn't diminish the usefulness of the architecture. Jamming the logic for processing input and the logic for displaying it into one "component" doesn't seem like an improvement -- that will just make it hard to change the presentation when you need to.

To me, the bottom line is that a web architecture must support having a designer who doesn't know Perl working on the HTML. Template oriented structures like MVC do this well. Your architecture doesn't look like it will.

In reply to Re: Why I dislike the MVC implementations in Web by perrin
in thread Why I dislike the MVC implementations in Web by ruoso

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.