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.
  • It is not going to die. You are falling for the fallacies of distributed computing [java.net].

    There is a reason that HTTP was successful and all the stateful protocols that were around at the time or long before it were not. HTTP is beautiful. Learn it and understand it instead of trying to use it like an RPC mechanism which it is not. See, f.ex, How I explained REST to my wife… [naeblis.cx]

    • by mdxi (4658) on 2005.05.29 12:24 (#40789) Homepage Journal
      Numbers 3 and 7 are basically true these days, as long as you're not trying to do something really stupid. Number 8 is true -- TCP/IP has killed all competing protocols. The rest were clearly said with LANs, and not the internet, in mind. Only a Microsoft would make those kind of assumptions these days.

      No, there definitely has to be a better way to do this kind of thing. There just has to be.
      • No, bandwidth is not infinite, not now, nor is it ever going to be. “Cost” need not (and indeed, for the purpose of that list, does not) have anything to do with money. And the wire protocol is only a fraction of homogenity.

        Maybe in a few decades when we’ll be used to writing for machines with dozens of CPUs in non-uniform configurations, writing distributed applications will no longer be a huge leap from writing local applications. But local applications on those systems will not be any