Yeah, here I am, working hard not to breach the DRY principle in my code, but once that pesky interweb thingy gets involved suddenly you're having to chase pointers and update stuff in 6 places at once. We should just have a Perl 6 organizational chart object which holds all the various relationships and work products etc, then every web page relating to Perl 6 can just be views onto that. It's a Simple Matter of Programming.
in reply to Re: Re: Perl 6 Involvement
in thread Perl 6 Involvement
Mmmm... 'just'... my favourite word when discussing programming projects; it's amazing how much complexity you can hide with it.