I'm not so sure that we're way far off. Currently, the big piece of our tech looks like:
- Getting nodes into and out of git as slimmed down XML
- being able to "bootstrap" an ecore site (such as perlmonks or E2) based out of github, so that multiple developers can work on the engine instead of patching the nodes in the database
If the underlying libraries are in source control anywhere, then we can see if there's anything that needs to be done to bring them together. I'd be happy to set up my github project so that perlmonks can submodule the tools section.
I don't know how much unification work it's going to take to port it, but if it's doable, it's certainly worth the gains in performance. Our compiled mode alone does wonders for performance on the dev branch.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.