use Perl

• Re: (Score:1)

  by Aristotle (5147)

  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]
  • Re: (Score:1)

    by mdxi (4658)

    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.
    • Re: (Score:1)

      by Aristotle (5147)

      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
• Sessions (Score:2)

  by bart (450)

  Web apps, as we're all aware, have no state, forcing the programmer to painfully reconstruct it via a horrible system of parameter passing and parsing, every single time the user does anything.

  You don't have to pass everything around, just pass an ID of where you currently are, and store the actual state data on the server.