Well, I have some ideas that might be interesting to me to build on that engine, if Perl is ever supported. I'm interested already in its architecture and start reading its docs. But I stop there. I have no time to try the provided SDK as it's written in Python and I know nothing about programming in Python.

I can't really imagine but I think I can see bigger thing about to happen, more than the inclusion Perl support (because it will probably just happen, sooner or later). Similiar but it's even more than opening accesss for Perl to Apache internal through mod_perl. On one hand, this could be a new market for developers to release their softwares, commercial or otherwise. Of course, in this case, we, Perl programmers, will compete with other programmers, but it's just the nature of business.

I can see that Ruby now outnumbers Perl vote count. Beside Perl, I also voted for JavaScript which is still out of top ten currently.

Regarding this so called Google AppEngine, can you see where Google is heading to after the fact that they launched Android? And will this give some impact to the ongoing development of Perl 6?

---

---

• 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.