Slashdot Mirror

← Back to Stories (view on slashdot.org)

PHP5 Coming Soon

Posted by krow on from the its-like-hee-haw-with-lazers dept.

Grip3n writes "PHP5 is well under development and a beta is expected out by March 2003 and released summer 2003. One of the more notable improvements which many PHP developers desired is a substantial improvement in PHP's performance. This is due to a new object model PHP5 will be introducing which handles objects by reference rather than by value. Co-creator Zeev Suraski states the new object model is inspired by the book, "Design Patterns"."

3 of 135 comments (clear)

  1. Re:Using design patterns by Tablizer · · Score: 0, Troll

    Obligatory design pattern counter-opinion:

    http://www.geocities.com/tablizer/prpats.htm#for mu las

    Quote of a quote:

    "In software engineering, duplication of something is often considered a sign that more abstraction or factoring is needed. Duplication should generally be refactored into one or fewer spots to simplify the code and localize changes to one or fewer spots. In other words, why do patterns have to be duplicated instead of just referenced for each usage? Do GOF patterns represent unnecessary duplication? Is all duplication bad?"

    This question:

    "In other words, why do patterns have to be duplicated instead of just referenced for each usage?"

    is almost as powerful as, "Why does God need a spaceship? [Trek]"

    Paul Graham has said that GOF patterns are a sign that "your abstractions are not powerful enough" (paraphrased).

    --
    Table-ized A.I.
  2. Re:I blame PHP... by RAMMS+EIN · · Score: 0, Troll

    Niches man, niches. Use PHP for generating webpages. Use Java for applets. If you're not writing applets, don't learn Java.

    --
    Please correct me if I got my facts wrong.
  3. Re:Using design patterns by Tablizer · · Score: 0, Troll

    So if you look at your design and it has something similar to a Singleton pattern...

    I don't think Singleton is a good example to look at. For one, it is very paradigm-specific. But other GOF patterns dictate how to set up the data/state. In procedural/relational thinking, you just issue a query against (mostly) pre-existing tables rather than build up a code-structure from scratch to perform such. I find formulas (queries) more compact and less disruptive to the larger app code structure. It is like moving the wires (rewire) instead of moving the circuits themselves.

    Not exactly 100% factorization (one thing to reference), but much closer than GOF comes.

    --
    Table-ized A.I.