Your skill will accomplish what the force of many cannot |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Hey Moritz,
Thanks for the feedback. Any more greatly appreciated. > Security:
> Usefulness: why the heck do you need to run arbitrary code on a wiki page? Well, as another approximation, Parrodocs isn't really a wiki, it's sort of like a PHP (done right). (But please remember, this is again an approximation; please don't respond with "I hate PHP", because Parrodocs is really a squeakish Perl6/website IDE. Well, actually it's a platform for experimenting with non-linear communication. Well ... urgh. Part of the point of this meditation was to work out which part of the elephant to describe first next time I try.) > Maintainability: There's a reason why code and templates are usually separated, and that is maintenance. Newbies don't care about maintenance, and they'll be delighted that they can just write "Hello $mom" and it'll DWIM. In contrast, an advanced developer might want total separation -- perhaps an XML + XSLT solution. I think Parrodocs will cover both extremes and variants in between. I look forward to any further thoughts from my fellow Monks... In reply to Re^2: RFC: self hosting Perl 6 string wiki
by raiph
|
|