On Mon, Aug 1, 2011 at 11:20 AM, Gabor Szabo wrote: > > I won't post the entire newsletter but I will try to remember posting a link > to the archive every time I sent out the newsletter. Heck I might even put > together and RSS feed for the RSS junkies :)
I thought the comment by Peter Makholm on your post ( https://plus.google.com/102810219707784087582/posts/VTqbHWJJZd5 ) was right on the money and that a p5p summary would be a great addition to your newsletter. Since I can't let you have all the fun, for this week at least, I whipped something up so maybe you can add it to your newsletter. Or Christian could if he starts writing it - he'll do a far better job than me for sure. See first thread below for more details. -- The Start Here's a rough summary of p5p "interesting threads" from aboutish last week. Christian Walde started an interesting thread titled "On the sad state of communicating future perl core development intentions"[1]. The thread quickly turned to the direction of "missing weekly p5p summaries". Personally I feel there's something of a missed oppurtunity there (since looking at past development is not quite the same as detailing future directions), however there was no lack of good intentions and the discussions were very positive from all who commented. Finally Christian Walde volunteered to create such a summary. Brian d Foy mentioned his posts about "most interesting features of each new Perl release over at The Effective Perler"[2]. Tom Christiansen gave links and some points for his "OSCON Great Unicode Shootout slides".[3] Father Chrysostomos started a thread on "Reducing code in pp_prototype"[4]. While code optimizations to the Perl core wouldn't seem like an interesting subject for a high-level p5p summary, I thought Nicholas Clark's reply in the thread was worth a mention: <blockquote> I'd suggest going for whatever is the clearest implementation. I think (in the general case) we should be optimising the perl core code for maintainability. People who can fix bugs are a far more limited resource than computers. Making the code clearer (without unduly making it larger or slower) should mean that it's easier to see opportunities to make other optimisations, particularly at broader design level. </blockquote> Reverend Chip linked to an interesting article about the Linux kernel and code complexity[6]. Jess Robinson sent a large "Patch for discussion - Cross-compiling (for Android)"[7]. Considering the rising importance of and market share of Android, I think this is important work. [1] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175110.html [2] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175132.html [3] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175113.html [4] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175163.html [5] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175245.html [6] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175276.html [7] http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg175302.html Disclaimer - this summary is a completely subjective work based on the (largly uninformed) personal opinions of the writer and in no way reflects the true importance of any threads posted to p5p during the last week. It also plays very fast and loose with the definitions of the words "last" and "week". -- The End Note - after I wrote all of the above I went through my p5p gmail folder to see if I missed anything. Some threads were started long ago and still ended last week, was easy to miss those. Also the above nntp archive seems to miss some messages, such as: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2011-07/msg01263.html Which is nowhere to be found on the nntp thread page: http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg174912.html Should we in the future summarize from the xray archives? Or is there another place? Regards, Offer Kaye _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
