I don't know anything about Comet or WebSocket, and the mojolicious homepage doesn't target these sales points at all. In conclusion mojolicious.org is not targeting me -- the early adopter type who *already* uses an mvc framework that he is fairly happy with, not to say I couldn't be more happy with Mojolicious. Instead you're doing what everyone is still doing by trying to target the dwindling audience of PHP users. That's what I see as the fault here. Your homepage is not noticeably different from any other mvc framework with generators.
No offense, lets examine my thought process as I traverse through your features:
* Full stack HTTP 1.1 client/server implementation (nothing new. s
+ales point in 2003).
* Builtin async io and prefork servers (cough?? explain.).
* CGI and FastCGI support (nothing new. Catalyst too).
* Code generators (Catalyst too. expired sales point in 2003).
* Very clean object oriented API (Catalyst too. subjective).
* Pure Perl (at best a moot point) without any hidden magic (which
+ is what everyone claims).
* Example MVC web framework (Catalst, Maypole, Jifty et al?) named
+ Mojolicious (the name has no bearing) (aka. Perl on Rails).
-
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.
|