Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re^7: Shouldn't JSON be faster?

by BrowserUk (Patriarch)
on May 31, 2010 at 12:34 UTC ( [id://842405]=note: print w/replies, xml ) Need Help??


in reply to Re^6: Shouldn't JSON be faster?
in thread Shouldn't JSON be faster?

HP-UX 10.20, considered dead, abandoned by HP years ago.I still make perl available in software depots for this OS on my website for users of this OS.

Did it ever occur to you that maybe HP had good reasons for dropping support of this ancient OS? And that by persisting in supporting it, you are creating the problem? ( Are you up for supporting MS C v6.0a for OS/2 also? I still have the diskettes.)

besides the silly // comments that should never have been added to ANSI-C.

And there it is. You want the world to comply to your archaic preferences, despite that your preferences are contrary to those adopted by the rest of the world. Look to thy self.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^8: Shouldn't JSON be faster?
by Tux (Canon) on May 31, 2010 at 12:52 UTC

    HP probably had good reason. My guess is not that the OS sucks, but a shortage of resources. Besides: they are commercial, we are volunteers.

    Essentially it is the same problem with any software. We still get bug reports for perl-5.6. We then tell those users to upgrade to a more recent version of perl, but sometimes users can't or are not allowed. Why they can't or why they are not allowed is way beyond our control.

    IMHO the perl community has alwys tried to still answer those questions, in my experience in a very polity way.

    Sometimes the people that help (and I consider you one of those) even propose patches that will never be applied to recent code, but only fix old problems. Those patches might be just references to (git) commits with comments like "This has already be fixed for more recent versions of perl/this module in a patch that you can fine here".

    So, I don't consider me a source of a problem, but a small resource to help those in need. I cannot force them to upgrade hardware or OS, but I can encourage them to use more recent versions of my/our favorite language: perl.

    OT: we're not discussing my personal preferences here. That could warrant a new thread indeed :) and I can assure you we won't agree on a lot of things!


    Enjoy, Have FUN! H.Merijn
      This is why he deleted your bug report rather than rejecting it by the way. You've effectively hijacked this thread, you refuse to understand that some people want to use modern language features (which is a-ok and totally allowed) and you just refuse to give up or create a fork. Personally, I figure I might end up deleting your bug report too. It might take me longer to get to that point, but I at least understand now why Marc just deleted it and promised to repeat. Cheers to you for effectively proving his point.

      -Paul

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://842405]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2024-04-25 19:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found