Wet blanket time. This does sound interesting but without code and docs to peek at it also sounds very much like the legacy system I'm working with now -- an object, meta-data repository API -- which is awful and strongly resistant to improvement or feature additions because anything that doesn't go through the API as expected will break something.
So, while you write "it's loosely coupled," I read "it's entirely and completely self-bound." I don't argue that that's a design mistake or could even be beautiful and extensible allowing one follows its rules; without seeing it in action or seeing what it does when it hits a corner case or an unexpected feature request it sounds a bit vaporesque.
Post some code when you can. :) I'd love to start to learn to do Moose/MOP correctly. I've only tinkered with it and I know I'm not getting as much out of it as it can provide.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
