Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • > Throwing away their numbering system

    I think they wanted to be able to use three numbers: major, minor, patch. To stick with a leading "1.", that would mean release numbers like "1.7.1.2".

    > throwing away their excellent logo

    Are you referring to the WWII image? It is too complicated to shrink to a small size. Some people don't like the association with war.

    I'm not a big fan of the new logo, but I don't really care that much about it either.

    > They're going to cram in more features

    I won't say anything about PAM, since it doesn't address my needs at all. Presumably it meets someone's needs, or Core wouldn't want it in.

    As for the other features, I expect them to come in rather slowly and carefully. For me, 2.0 has worked fine , but then again I haven't been stressing the new stuff (SMP and threads). It seems like NetBSD is doing time-gated releases, rather than feature-gated release, given that they're about to ship 3.0 without much in the way of new stuff (PAM -- what else?). That should prevent a FreeBSD5-style never-ending development cycle.

    If you want a maintained NetBSD branch with no major features being added, OpenBSD might be appropriate.

    Though I too would rather have NetBSD-1.5 with security patches.