Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I also use Haskell and Common Lisp, and they both have non-beautiful websites. I care about what a langauge will help me do, not whether or not some websites that talk about those languages are pretty. This, I believe, is because I am over the age of 4.
    • Those who ignore marketing are doomed to repeat it.

      No offence, but marketing is not evil and ignoring it doesn't help. And citing Haskell and Common Lisp as examples of languages which don't need pretty Web sites is, well, you know :)

      • Marketing is evil and like Bill Hicks said to PR-guys: kill yourself. you satans little helper and there is no rational behind what you are doing.

        but on the othe hand, its no marketing, to have a nice looking and usefull site with fresh content. while I understand jrockaway attitude, there lies no problem because such a site would not scare him away from perl, but he would appreciate it, when wie achieve something good. But perl noobs could be scared away, which raises the question what is it we have a si
        • I reiterate Ovid's statement, marketing is not evil. There is good marketing and bad marketing, but dismissing it as evil is to miss the point entirely.

          use.perl was an active and very current site when I joined, it's only real problem is that it doesn't have a dedicated active development team, in the way that PerlMonks has. The code is based on SlashCode and as far as I'm aware that's still the case. The data might not be available, but the code is there. Unfortunately no-one has felt moved to work on improving it and keeping up with the latest trends and features, at least not to the degree that everyone seems to be wanting these days.

          Many other blog sites have come into being since and have embraced the world of AJAX, customisation, etc, because they've been designed that way from the beginning. Unfortunately use.perl was designed before all the new trends came along. Making it fashionable and evolving it requires a team of enthusiastic developers.

          However, coming back to marketing, whether you like it or not a website is part of marketing. use.perl is part of the promotion of the Perl developer community. Currently everyone posting to use.perl is part of that community already, but they are a small part of the Perl user community as a whole. Now while the whole of the user community are unlikely to want to join use.perl and post to it, there are other things that can (and often do) feature on use.perl that would interest them as a reader. Presenting a website that doesn't provide them with a clear front page, or has a confusing navigation, is likely to put them off coming back and using the site as a valuable resource.

          The collective wisdom on use.perl is a valuable resource that is largely hidden when you first view the site. It's only once you get involved that you become more aware of the discussions, ideas, thoughts, projects among many other things that reside here. Maybe use.perl only needs to reorganise the way it promotes it's content, possibly add some features that aid usability, but it also needs someone to do it :)