Re: Emergency Social - brian d foy
This is tonight. Lovely day to go to the Founders Arms :-/ See you there. On 08/19/2011 08:05 AM, Dave Cross wrote: Perl writer, trainer and all-round nice guy, brian d foy is passing through London next Tuesday (23rd Aug). I'll be meeting him for a drink or three at the Founders Arms[1] at about 7pm. You're all welcome to join us. Dave... [1] http://london.randomness.org.uk/wiki.cgi?Founders_Arms%2C_SE1_9JH
Re: Emergency Social - brian d foy
On Tue, Aug 23, 2011 at 08:09:47AM +0100, Dave Cross wrote: This is tonight. Lovely day to go to the Founders Arms :-/ I wish I could be there. Enjoy! dha -- David H. Adler - d...@panix.com - http://www.panix.com/~dha/ In my opinion, there's nothing in this world beats a '52 Vincent and a red headed girl - James Adie
Re: Getting cpan's Oracle DBD to work properly on i386 is proving a bit tricky
* Chris Benson (chr...@ccandc.org) [110822 21:29]:
On Mon, Aug 22, 2011 at 05:17:07PM +0100, Paul Branon wrote:
Hi Guys,
Does anyone know where I can get help getting oracle DBD to work? I'm on
Intel Solaris 10
and Oracle comes with an AMD64 binary. It runs fine on my system. I can
connect to oracle
with no problems at all. Then I install oracle DBD which installs just fine
But when I try to
connect to the database I get wrong ELF class. Because libclntsh.so.10.1 is
a 32 bit binary.
Uhm for my sins, I've got:
root@selfservice:/usr/local # uname -a
SunOS selfservice 5.10 Generic_142901-07 i86pc i386 i86pc
oot@selfservice:/usr/local # file
/usr/local/oracle/product/instantclient_10_2/libclntsh.so.10.1
/usr/local/oracle/product/instantclient_10_2/libclntsh.so.10.1: ELF 32-bit
LSB dynamic lib 80386 Version 1, dynamically linked, not stripped
root@selfservice:/usr/local #
... and I think what makes it possible:
root@selfservice:/usr/local # file /usr/local/bin/perl
/usr/local/bin/perl:ELF 32-bit LSB executable 80386 Version 1 [FPU],
dynamically linked, not stripped, no debugging information available
root@selfservice:/usr/local #
Which was either from sunfreeware.com or locally built.
On some SPARC systems where there's a full 64bit Oracle installed, I've
resorted to ensuring that I've set
ORACLE_HOME=/export/home/oracle1020/product/1020/client_1/
LD_LIBRARY_PATH=$ORACLE_HOME/lib32
export ORACLE_HOME LD_LIBRARY_PATH
before starting or where I can't/don't trust the environment to:
BEGIN {
# needs to before loading the DB modules
$ENV{ORACLE_HOME} ||= '/export/home/oracle1020/product/1020/client_1';
# LD_LIBRARY_PATH needed because we're on a 64bit Oracle now
$ENV{LD_LIBRARY_PATH} ||=
$ENV{ORACLE_HOME}/lib32:$ENV{ORACLE_HOME}/network/lib32;
}
But again this is with a 32-bit Perl.
# file /usr/local/bin/perl
/usr/local/bin/perl:ELF 32-bit MSB executable SPARC Version 1,
dynamically linked, not stripped
I guess what I need is literally the answer.
Install a 32-bit Perl has been my solution. I'll need to look at
this again soon for the next technology refresh though :-/
I'm hoping it won't be as irritating on RHEL/OUL, but my first attempts
to setup an application server for Oracle 11g ended up rebuilding the
whole system as 32-bit because the application vendor had linked their
app against a 32-bit libclntsh and 32-bit Oracle 11g won't install on a
64-bit o/s ...
Looking at
http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html,
Oracle provides Solaris x86 and Solaris x86-64 builds of the
instant client.
HTH
--
Chris Benson
Simon Matthews
Re: Emergency Social - brian d foy
Quoting David H. Adler d...@panix.com: On Tue, Aug 23, 2011 at 08:09:47AM +0100, Dave Cross wrote: This is tonight. Lovely day to go to the Founders Arms :-/ I wish I could be there. Enjoy! There was a tiny amount of sarcasm in what I wrote. It was pissing down as I wrote it. Hoping it dries out a bit before this evening. Dave...
Writing About Perl
So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Cheers, Dave...
Re: Writing About Perl
On Tue, Aug 23, 2011 at 11:39 AM, Dave Cross d...@dave.org.uk wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Perl's strength is as a glue language - gluing together the wealth available on CPAN. So I'd like to see an article that built a service that did quite a bunch of complicated things by gluing together CPAN modules... -P
Re: Writing About Perl
Developments in Moose, modern web frameworks, influences of Perl 6? On Tue, 2011-08-23 at 11:39 +0100, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Cheers, Dave...
Re: Writing About Perl
On Tue, Aug 23, 2011 at 11:57:49AM +0100, Peter Sergeant wrote: On Tue, Aug 23, 2011 at 11:39 AM, Dave Cross d...@dave.org.uk wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Perl's strength is as a glue language - gluing together the wealth available on CPAN. So I'd like to see an article that built a service that did quite a bunch of complicated things by gluing together CPAN modules... I rather write about gluing together services. Services (like databases, email, http, etc) the readers are familiar with. Otherwise, it sounds to much as here we have a bunch of toys made out of play-doo; look how awesome this play-doo is, we can use more play-doo to glue them all together. Abigail
Re: Writing About Perl
I think that devs are interested in tools that let them get things up and running with little effort, so perhaps an article explaining how easy it is to use catalyst/dancer/mojo + dbic + plack (with a bit of moose thrown in) using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) to get a web app up and running in a few minutes. That was the appeal of ruby and rails as far as I can make out. Cheers, Pete On 23/08/11 11:39, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Cheers, Dave...
Re: Writing About Perl
On 23 August 2011 12:24, Pete Smith p...@cubabit.net wrote: I think that devs are interested in tools that let them get things up and running with little effort, so perhaps an article explaining how easy it is to use catalyst/dancer/mojo + dbic + plack (with a bit of moose thrown in) using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) to get a web app up and running in a few minutes. That was the appeal of ruby and rails as far as I can make out. I agree. Show how to write a web service running on Dotcloud using Dancer . Regards, Peter
Re: Writing About Perl
I agree. Show how to write a web service running on Dotcloud using Dancer . Making use of modules from CPAN, which make it even easier to get stuff done? Sawyer created a small presentation after a joke site I created, to showcase that exact thing: http://www.slideshare.net/xSawyer/your-first-website-in-under-a-minute-with-dancer Take a module (in my case, Text::UpsideDown), create a web interface to it in minutes. I am not sure this is what the wide audience of a Linux journal would like to read about how Perl has changed in the past decade, though.. --- Marco Fontani Glasgow Perl Mongers - http://glasgow.pm.org/ Bitcoin: 1QA1K3Ghz9AuJ8na6JKJVudEko3WKx1xC2 Join the RackSpace Cloud at: http://www.rackspacecloud.com/277.html
Re: Writing About Perl
On Tue, Aug 23, 2011 at 12:24:05PM +0100, Pete Smith top-posted: I think that devs are interested in tools that let them get things up and running with little effort, so perhaps an article explaining how easy it is to use catalyst/dancer/mojo + dbic + plack (with a bit of moose thrown in) using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) to get a web app up and running in a few minutes. That was the appeal of ruby and rails as far as I can make out. So, the point of the assignment (which is to show how Perl has moved on in the last 10 years) is going to be after 10 years, we now can do what Ruby on Rails can? On 23/08/11 11:39, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Abigail
Re: Writing About Perl
On Tue, 2011-08-23 at 11:39 +0100, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? 10 years ago the popular view was the perl always ended up with an unmaintainable code base and that it was not very easy to implement. I'd suggest something to show how the use of CPAN makes it easy to produce big projects without writing lots of code and that the code produced is easy to maintain. I'd also consider doing something on top of Plack and a popular web framework.
RE: Getting cpan's Oracle DBD to work properly on i386 is proving
Paul Branon paulbra...@googlemail.com wrote: Does anyone know where I can get help getting oracle DBD to work? I'm on Intel Solaris 10 and Oracle comes with an AMD64 binary. It runs fine on my system. I can connect to oracle with no problems at all. Then I install oracle DBD which installs just fine But when I try to connect to the database I get wrong ELF class. Because libclntsh.so.10.1 is a 32 bit binary. I've tried all kinds of things. But I think in the end I'm really going to have to talk to someone who's recently installed oracle (preferably 10g) on intel solaris 10 and then got cpan oracle DBD to talk to it. I've had lots of great suggestions from people but I can't get any of them to work. I guess what I need is literally the answer. Are you compiling from scratch? DBD::Oracle is annoying because it has to be compiled against the same Oracle Client that you are using to connect. Here's a quote from http://search.cpan.org/~pythian/DBD-Oracle-1.28/Oracle.pm First off you will have to tell DBD::Oracle where the binaries reside for the Oracle client it was compiled against This is really quite annoying and DBD::Sybase, for instance, does not have this limitation. For my sins (which are varied and multitudinous), I am doing an upgrade from Oracle 10.2 to Oracle 11.2 at the moment. The perl (32 bit 5.6 and 5.8) libraries were compiled against Oracle 8.1.7 - and the 11.2 server only (officially) supports Oracle 9 clients and above. We only have the 64 bit 11.2 Oracle client libraries available so, as switching to 64 bit would cause all sorts of other problems, I am using 10.2.0.4 32 bit libraries and taking the opportunity to move to 5.12 of perl. 10.2.0.4 is the first version of the Oracle client that, despite the version, was compiled with the Oracle 11 code base (10.2.0.3 was the last using the Oracle 10 code base). If you have the choice, I would suggest you use at least 10.2.0.4 to postpone any future perl upgrade issues. Regards Chris
Re: Writing About Perl
On 23/08/2011 19:39, Dave Cross wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? What's changed in the past ten years? I don't think this is going to be a very popular answer, but: not much. At least, not much that's user-facing. Sure, there have been some minor adjustments to the language, but nothing so exciting that it's worth sharing with people who aren't true believers already. Ten years ago, design and implementation of Perl 6 had begun in earnest. 'nuff said. Ten years ago, CPAN was considerably smaller than it is today, but looking back over my code from 10 years ago, at the time we *were* using CPAN modules for the majority of heavy-lifting in our applications. That hasn't changed. The Moose/Modern Perl/whatever doctrinaire style is new; 10 years ago, TMTOWTDI still meant something. You could try rewriting an old piece of code in Moose and showing how different it is. Lightweight web frameworks are new, and are probably the only thing worth screaming about to the world at large. In all honestly, I don't think there are, unfortunately, too many areas where Perl has been the driver of technological change over that time; we're generally pretty good at providing interfaces to other interesting things that are going on, and maybe that is Perl's role and we should rejoice in it. It doesn't make great marketing copy though. There. That should be enough for the simian terpsichory to begin, out of which might come some better suggestions.
Re: Writing About Perl
On Tue, Aug 23, 2011 at 11:39:57AM +0100, Dave Cross wrote: [...] If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? I would *not* bang on about Perl's web technologies. People interested in that are already going to be playing with the likes of Django or Rails which are perfectly good tools and Perl's tools aren't sufficiently better for most users that it's worth a switch. This being a Linux magazine, I'd focus more on system administration and tool-building, and odd ways to use Perl and Perl's tools to solve non-Perl problems. For example, there's the prename command that uses Perl one-liners to mangle filenames for renaming: I often use it to strip crap from and canonicalise filenames. TAP and prove is handy for testing non-Perl things - I use it to test some C++ stuff. POD is much less painful to write than raw nroff. ack is bloody handy. Look how much useful stuff Perl has done without having to write a line of code! Now you've piqued the readers' interest, you can save the code-writing for the second article in the series that they'll inevitably ask you to write...
Re: Writing About Perl
On Tue, Aug 23, 2011 at 12:48 PM, Jason Clifford ja...@ukfsn.org wrote: On Tue, 2011-08-23 at 11:39 +0100, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? 10 years ago the popular view was the perl always ended up with an unmaintainable code base and that it was not very easy to implement. I'd suggest something to show how the use of CPAN makes it easy to produce big projects without writing lots of code and that the code produced is easy to maintain. I'd also consider doing something on top of Plack and a popular web framework. As someone who used to mostly code Perl but mostly doesn't anymore (and re-joined this list to find out more about what the state-of-the-art in the world of the Camel was) this is the kind of thing I'd be interested in. I do read those kind of magazines, but no idea if I'd be the target audience for the article. Matt
Re: Writing About Perl
Pete Smith writes: using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) ... I'd say the opposite, that cpanm is one of the major highlights of recent developments in Perl. Somebody who's previously been frustrated by installing Cpan modules can be impressed by how cpanm just works -- and indeed by how easy it is to install cpanm in the first place. And given that many modules (or versions of modules) become popular faster than many users update their servers, suggesting people restrict themselves to whatever modules come with their distribution may not be helpful. For what it's worth, I have: PERL_CPANM_OPT='--sudo --prompt' I think --sudo is definitely worth mentioning when introducing somebody to cpanm, since the casual user probably only has one Perl interpreter installed and wants modules to be system-wide. Smylers -- http://twitter.com/Smylers2
Re: Writing About Perl
So there's three articles: 1. Mashups using CPAN modules 2. Modern perl, Moose, DBIC 3. Cool scaffold On 23 Aug 2011, at 13:27, Smylers wrote: Pete Smith writes: using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) ... I'd say the opposite, that cpanm is one of the major highlights of recent developments in Perl. Somebody who's previously been frustrated by installing Cpan modules can be impressed by how cpanm just works -- and indeed by how easy it is to install cpanm in the first place. And given that many modules (or versions of modules) become popular faster than many users update their servers, suggesting people restrict themselves to whatever modules come with their distribution may not be helpful. For what it's worth, I have: PERL_CPANM_OPT='--sudo --prompt' I think --sudo is definitely worth mentioning when introducing somebody to cpanm, since the casual user probably only has one Perl interpreter installed and wants modules to be system-wide. Smylers -- http://twitter.com/Smylers2
Re: Writing About Perl
On Tue, Aug 23, 2011 at 2:02 PM, Simon Cozens si...@simon-cozens.orgwrote: On 23/08/2011 19:39, Dave Cross wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? What's changed in the past ten years? I don't think this is going to be a very popular answer, but: not much. At least, not much that's user-facing. Sure, there have been some minor adjustments to the language, but nothing so exciting that it's worth sharing with people who aren't true believers already. Ten years ago, design and implementation of Perl 6 had begun in earnest. 'nuff said. Ten years ago, CPAN was considerably smaller than it is today, but looking back over my code from 10 years ago, at the time we *were* using CPAN modules for the majority of heavy-lifting in our applications. That hasn't changed. The Moose/Modern Perl/whatever doctrinaire style is new; 10 years ago, TMTOWTDI still meant something. You could try rewriting an old piece of code in Moose and showing how different it is. Lightweight web frameworks are new, and are probably the only thing worth screaming about to the world at large. In all honestly, I don't think there are, unfortunately, too many areas where Perl has been the driver of technological change over that time; we're generally pretty good at providing interfaces to other interesting things that are going on, and maybe that is Perl's role and we should rejoice in it. It doesn't make great marketing copy though. There. That should be enough for the simian terpsichory to begin, out of which might come some better suggestions. CPAN still is a driver of techno-social change. Other repositories are maybe catching up - but CPAN is still on the frontier and it is the one that is being copied. Open Source has the chronic malaise of fragmentation, of disagreement, of debating all decisions and forking. The Perl community is not exception - and it is even worse in the lack of leader-library like Rails that would align the development. It also might seem that TIMTOWDI only leads to further fragmentation - but it also forces us to reject our assumptions and thus leads us to discover what is arbitrary and what is objective. One of these discoveries is the reliance on tests, -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/
Re: Writing About Perl
On 23/08/11 12:45, Abigail wrote: So, the point of the assignment (which is to show how Perl has moved on in the last 10 years) is going to be after 10 years, we now can do what Ruby on Rails can? Hey, don't take it so literally. My point was that being easy to get up and running is what made RoR so popular.
Re: Writing About Perl
If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? I was really impressed by the AutoCRUD but as someone's pointed out, you run the risk of saying Look we can do what others have been able to do 10 years ago. Some sysadmin might suit that target audience. I have heard talk of perl on Android, that would be fun. Mobile apps are the rage and I'm not sure the readers of a popular Linux magazine are going to be interested in Moose+DBIC. Dp.
Re: Writing About Perl
On Tue, Aug 23, 2011 at 11:39 AM, Dave Cross d...@dave.org.uk wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? I'd sit down and re-read Modern Perl from cover to cover and take notes of things that are worth mentioning. You've also got a chance to throw in some one liners here: Which I learned about at YAPC::Europe, one of Perl's annual conferences I'm using Perl 5.14 (a new stable version of Perl is released on average once a year) Mark.
Re: Writing About Perl
On Tue, Aug 23, 2011 at 13:59, Pete Smith p...@cubabit.net wrote: Hey, don't take it so literally. My point was that being easy to get up and running is what made RoR so popular. As it did PHP before that...
Re: Writing About Perl
Quoting Smylers smyl...@stripey.com: Pete Smith writes: using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) ... I'd say the opposite, that cpanm is one of the major highlights of recent developments in Perl. Somebody who's previously been frustrated by installing Cpan modules can be impressed by how cpanm just works -- and indeed by how easy it is to install cpanm in the first place. I agree with that. But I'm sure that at the level this hypothetical article is aiming at, installing distro packages is going to be far better than any solution involving CPAN. If only because mixing CPAN-installed modules and distro-installed modules is potentially a recipe for disaster (and I'm _not_ going to cover installing your own Perl). And most distros are far better at tracking newer versions of interesting CPAN modules these days. So I can't really see it being a problem. Cheers, Dave...
Re: Writing About Perl
Sent from my iPhone On 23 Aug 2011, at 15:25, Dave Cross d...@dave.org.uk wrote: Quoting Smylers smyl...@stripey.com: Pete Smith writes: using distro packages (cpan probably frustrates newbies to perl if installation / tests fail) ... I'd say the opposite, that cpanm is one of the major highlights of recent developments in Perl. Somebody who's previously been frustrated by installing Cpan modules can be impressed by how cpanm just works -- and indeed by how easy it is to install cpanm in the first place. I agree with that. But I'm sure that at the level this hypothetical article is aiming at, installing distro packages is going to be far better than any solution involving CPAN. If only because mixing CPAN-installed modules and distro-installed modules is potentially a recipe for disaster (and I'm _not_ going to cover installing your own Perl). And most distros are far better at tracking newer versions of interesting CPAN modules these days. So I can't really see it being a problem. Cheers, Dave... Larger orgs are rubbish at keeping up. So perlbrew, cpanm and local::lib are big wins in environment
Re: Writing About Perl
On Tue, Aug 23, 2011 at 11:39:57AM +0100, Dave Cross typed: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Tell them to wait two years and then give them one about rakudo. -- Steve Mynott st...@gruntling.com
Re: Writing About Perl
Dave Cross said:
So, purely hypothetically...
If a popular Linux magazine had given you the opportunity to write a
3000 word article giving a practical project-based demonstration of
how Perl had moved on in the last ten years, what would you do? What
would you write about?
fantasy_mode
I'd perhaps say that TIMTOWTDI has resulted in years of experimenting
and trying and failing and learning, leading to a CPAN and a Perl
community that is better and stronger than ever.
Being the laughing stock (so to speak) of dynamic language communities
for many years have been a useful motivation for introspecting and
reinventing ourselves. It's like the the big and shy nerd in class
taking years of beating by the cool kids, and when the penny finally
drops, he quietly says No, my friends, there's actually a lot of good
going on with me and I'm not going to take your abuse any more. Now go
fuck *yourself*, thankyouverymuch.
/fantasy_mode
:-P
- Salve (Oslo.pm)
--
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$='};{';@_=unpack(C*,unpack(u*,':4@,$'.# s...@foo.no
'2!--5-(50P%$PL,!0X354UC-PP%/0\`'.\n));eval {'@_'}; __END__ is near! :)
Re: Writing About Perl
On Tue, Aug 23, 2011 at 12:59:42PM +0200, Job van Achterberg wrote: On Tue, 2011-08-23 at 11:39 +0100, Dave Cross wrote: So, purely hypothetically... If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? Developments in Moose, modern web frameworks, influences of Perl 6? None of those are of any interest to people not currently using perl. Web frameworks in particular is so what, what's so special about that? -- David Cantrell | Bourgeois reactionary pig Your call is important to me. To see if it's important to you I'm going to make you wait on hold for five minutes. All calls are recorded for blackmail and amusement purposes.
Re: Writing About Perl
On Tue, Aug 23, 2011 at 03:25:25PM +0100, Dave Cross wrote: And most distros are far better at tracking newer versions of interesting CPAN modules these days. So I can't really see it being a problem. I'm not sure they do a good job of tracking *interesting* modules. They might track frameworks like Catalyst and important things like DBIx::Class and DateTime, but those aren't very interesting and don't do much without the interesting but unpopular bits n pieces that actually make your application unique. -- David Cantrell | Godless Liberal Elitist I'm in retox
Re: Writing About Perl
On 23 August 2011 13:02, Simon Cozens si...@simon-cozens.org wrote: On 23/08/2011 19:39, Dave Cross wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? What's changed in the past ten years? 10 years?... in no particular order.. Core Perl: -- Regular release cycles Setup stuff: - CPAN::Mini CPAN::Mini::Inject CPAN::Webserver local::lib cpanm perlbrew Best practices: -- Task::Kensho DBIx::Class Modern Perl (the book as well as the ethos) Moose / Moo MooseX::App::Cmd Testing / test results: --- http://www.cpantesters.org/ Test::Most Websites: -- https://metacpan.org/ http://perldoc.perl.org/ http://www.perl.org/about/whitepapers/ might also be useful to link to, although we should probably get some more sysadmin related papers in there (anyone interested let me know). Frameworks: --- Dancer Catalyst Plack with both of them + 160 Plack::Middleware modules to help Sysadmins not worry about server specific configuration. Web server infrastructure: - Starman (very fast) Mogilefs - distributed redundant file system These two work great for us at work (although there are more alternatives now): Perlbal - load balancer / proxy TheSchwartz - queue manager * * Sorry - I don't have time to write anything more than a cursory list, but there's at least a couple of articles in there, Leo
Re: Writing About Perl
On Tue, Aug 23, 2011 at 4:21 PM, Salve J Nilsen sjn-london...@pvv.org wrote: I'd perhaps say that TIMTOWTDI has resulted in years of experimenting and trying and failing and learning, leading to a CPAN and a Perl community that is better and stronger than ever. John Siracusa makes some good points along these lines in Hypercritical (his weekly podcast with the pro-Ruby, Perl doubting, Dan Benjamin) Essentially all these other languages should learn from our mistakes - we've done the years of screwing up for them! If you're interested, the meat of the discussion happens way back in episodes 18. as part of a series where he responds to the pro-PHP comments made by the pro-PHP programmer Marco during his Build and Analyse podcast (also hosted with Dan on the same network.) http://5by5.tv/hypercritical/18 I really like the debates in these podcasts because they feature a Ruby, Perl and PHP guy actually sensibly stating their case and presenting good, coherent arguments and eventually finding middle ground. Mark.
Re: Writing About Perl
Quoting Leo Lapworth l...@cuckoo.org: On 23 August 2011 13:02, Simon Cozens si...@simon-cozens.org wrote: On 23/08/2011 19:39, Dave Cross wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? What's changed in the past ten years? 10 years?... in no particular order.. [ excellent list snipped ] Sorry - I don't have time to write anything more than a cursory list, but there's at least a couple of articles in there, There would certainly be several articles in that list if the title of the article was something like what has changed in Perl in the last ten years. Unfortunately, the article (perhaps articles, we'll see) needs to be project based. That means it needs to go from nothing to a cool working program in less than 3000 words - taking in modern Perl and best practices en route. If you want to see what we're up against, see: http://perlhacks.com/2011/04/an-open-letter-to-linux-format/ Cheers, Dave...
Re: Writing About Perl
On 23/08/2011 19:39, Dave Cross wrote: If a popular Linux magazine had given you the opportunity to write a 3000 word article giving a practical project-based demonstration of how Perl had moved on in the last ten years, what would you do? What would you write about? That means it needs to go from nothing to a cool working program in less than 3000 words - taking in modern Perl and best practices en route. How about extending something instead of starting from nothing? Installing / using / extending Domm's App::Timetracker ( https://metacpan.org/release/App-TimeTracker) might make an interesting article. He gave a talk about it at YAPC::EU http://yapceurope.lv/ye2011/talk/3391(slides: http://domm.plix.at/talks/2011_riga_app_timetracker/) Source could do with a few more comments for my personal tast, anyway - just an idea :) Leo
Re: Writing About Perl
On 23 August 2011 18:11, Leo Lapworth l...@cuckoo.org wrote: Installing / using / extending Domm's App::Timetracker ( https://metacpan.org/release/App-TimeTracker) might make an interesting article. He gave a talk about it at YAPC::EU http://yapceurope.lv/ye2011/talk/3391(slides: http://domm.plix.at/talks/2011_riga_app_timetracker/) Oh that's pretty cool. The git sync idea would go down well with Linux hackers. -Peter
