pmichaud: Is the printing "plasticy", such that having the design large and centered would be heavy and make your chest sweat? Or is it "dye-like", so that it adds little to the weight or breathability of the fabric?

pmichaud: If it was plasticy, I'd be less likely to buy anything in which the logo was much larger than the current "pocket-sized" look. But if it's non-plasticy, then having people be able to read it from 10 paces would be nice. :-)

I like white or light colored backgrounds for a full color logo ... and I can't wear black at all. Looks fricking awful on me. So I'd be happy if the shirt stayed basic white, or had that as an option at least.

If someone does decide to fix it, I'd move the download button up to being centered above the boxes, because the addition of the schwag box will make it a nice neat 3x2 block of boxes without having to "fill space" -- and it's better to have the download button be really obvious up top anyway.

okay. by tonight I expect I'll have all of the announcement files and stuff up-to-date; I'll give you the "go ahead" and you can do the release at your convenience anytime after that (hopefully while it's still 23 Jul *somewhere* in the world :-)

"sanction" means, popularly, "to endorse" and "to forbid" (but this is because it's was a loan word in Middle English, from French, from Latin, meaning "to ratify"). English is highly succeptible to usage-creep, and its users tend not to think very hard about what words are *defined* to mean. so don't try to think hard about it :)

rakudo: When we have a named slurpy param, we don't need to do a bindability check to see if there's matching named params since it accepts 'em all anyway. This lets us cache many multi-method dispatches again now methods get their *%_, winning back some performance.

I think it's sort of strange, that they released 1.x (I think of 1.x releases as "Ready for use in production"-releases, though I don't know wether this is also the case with parrot) without a most awesome, extensible optimization engine. Especially if you consider that it should be possible for languages with completely different paradigms to run on it.

moritz_: re different test syntax, I see the desirability of improvements, but all the suggestions I've seen are teh blech. either we're in a sweet spot wrt testing, or we're still waiting for the Big Idea to manifest itself.

PerlJam: (to digress from the current topic) regarding your regex tutorial: I find it *very* good, and have just one improvement to make: as soon as you introduce whitespaces as metasyntactic, the readable form should be the default

PerlJam: sure. note that I haven't bothered to list the types of the parameters and return types in my method Pod. I mostly talk about what the methods do. my target group is people who want to read about Druid but don't (yet) want to read the source.