The two are not unrelated. How many people start using PerlMonks who do not use Perl? (I know there are a few folks still kicking around here who no longer use Perl, but I'm talking about first-timers to the site.) | [reply] [Watch: Dir/Any] |
"How many people start using PerlMonks who do not use Perl?"
Judging by some of the post from new users, several.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] [d/l] [select] |
True, but at least they're trying to use Perl, even if they're not very good at it.
| [reply] [Watch: Dir/Any] |
As mentioned below in another users post, I see the health of Perl and PerlMonks as tightly coupled. There is really little to be complained about when it comes to PerlMonks. It is a great resource, compelling in many ways, and encompasses all the characteristics of a community, both good and bad.
Perl is a mature language, and as with all things: Familiarity breeds contempt. Or at least dismissive-ness. Newer languages tend to generate more attention, and if the language is reasonably functional and familiar in syntax, it will be around for a while. I would not be surprised if Perl has a Renaissance at some point. But maybe that is just wishful thinking on my part. But back to the main point, Perl and PerlMonks are inter-dependent as I see it. One will usually follow the other with some hysteresis between their independent trends.
...the majority is always wrong, and always the last to know about it...
A solution is nothing more than a clearly stated problem...
| [reply] [Watch: Dir/Any] |
> see the health of Perl and PerlMonks as tightly coupled.
I agree but that's not the point, husband and wife are also
"closely coupled" but they can improve their look independently.
PM could easily borough many design ideas from sites like stack overflow without fundamental code changes.
And most probably Perl would be envied for its attractive "partner" but that's another story.
| [reply] [Watch: Dir/Any] |