--
You received this message because you are subscribed to the Google Groups "PDXPHP" group.
To post to this group, send email to pdx...@googlegroups.com.
To unsubscribe from this group, send email to pdxphp+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pdxphp?hl=en.
-Mike
__________________
Michael Prasuhn
503.512.0822 office
mi...@mikeyp.net
http://mikeyp.net
best,
Andrew
> --
> You received this message because you are subscribed to the Google Groups "PDXPHP" group.
> To post to this group, send email to pdx...@googlegroups.com.
> To unsubscribe from this group, send email to pdxphp+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pdxphp?hl=en.
>
>
--
Andrew Embler
CTO, concrete5
concrete5.org : andrewembler.com : facebook.com/aembler : twitter.com/aembler
Why is it asinine? Wordpress had users on PHP 4, PHP 4 hadn't reached
end of life yet, so Wordpress made sure that those users were
supported while still moving the platform forward.
Wordpress has over 50 million blogs, and VC daddies with 44m+ invested
in them. It's all well and good to want to keep using the latest and
greatest, who in their right mind is going to say: "lets dump more
than half of our audience because their webhosts are slow to upgrade."
Don't get me wrong, as a software provider I very much want our
customers to upgrade when we have a new version, and with that hat on
I can totally recognize the "we only support recent versions" approach
of companies like Apple. concrete5 does basically require php5.2. But
we've got 70k sites not 50m and we've always required php 5+ so
telling people 5.1 won't cut it isn't a particularly difficult thing
to say...
As a software consumer, I only upgrade when I have some pressing need.
"If it ain't broke..."
The truth is surely somewhere in the middle, but there's a difference
between leading edge and bleeding edge and using the latest just
because it exists is a dubious strategy if it means you're losing
potential customers. I think using the most widely adopted version of
something is a pretty solid plan.
best wishes
Franz Maruna
CEO - concrete5.org
This reminds me of the whole "to support or not to support IE6" question (though nothing quite compares to the absolute horror that is IE6) and the main drag in trying to move forward are the larger companies where it's just ingrained in their systems and difficult to upgrade on such a large scale. As developers it would be fun and convenient to turn our backs on the old stuff but we're running along with countless other websites, servers, businesses, etc., so I personally feel it's best to be flexible, know the old and the new, and, for the sake of a paycheck, be comfortable living somewhere in between the bleeding edge and, well, PHP4.
Chris Forrette
http://www.chrisforrette.com
<plug> thats the hole we're trying to fill with concrete5 - something
that doesn't take a CS background to setup and get working, but also
doesn't create crap code and can be extended in a graceful way if you
know what you're doing </plug>
best wishes
Franz Maruna
CEO - concrete5.org
On Sep 29, 8:56�am, Brandon Savage <bran...@brandonsavage.net> wrote:Supporting the PHP 4 users wasn't asinine until PHP 4 went end of life. To CONTINUE supporting it is what is asinine.
Why do you think it's foolish for Wordpress to do this? (not trying to start some asshole internet flame war. I'm just curious and trying to avoid starting on The Work� this morning) -- Alan Storm http://alanstorm.com
Regardless, looks like PHP5 proponents will get their wish sooner
rather than later:
http://news.softpedia.com/news/WordPress-3-2-to-Drop-Support-for-PHP-4-and-MySQL-4-149109.shtml
best,
Andrew
On Wed, Sep 29, 2010 at 12:20 PM, Tony Freixas <tfre...@gmail.com> wrote:
> I don't know if it's foolish or smart, but there's a chicken-and-egg problem
> here.
>
> Some hosting services will update only when there is pressure to do so. Some
> developers will restrict themselves to an older platform just because not
> all hosting services support the newer stuff.
>
> By supporting PHP4, WordPress perpetuates PHP5. Make WordPress require PHP 5
> and the hosting services will upgrade.
>
> --
> Tony Freixas
> tfre...@gmail.com
>
> On 09/29/10 9:24 AM, Alan Storm wrote:
>
> On Sep 29, 8:56 am, Brandon Savage <bran...@brandonsavage.net> wrote:
>
> Supporting the PHP 4 users wasn't asinine until PHP 4 went
> end of life. To CONTINUE supporting it is what is asinine.
>
> Why do you think it's foolish for Wordpress to do this? (not trying to
> start some asshole internet flame war. I'm just curious and trying to
> avoid starting on The Work™ this morning)
>
> --
> Alan Storm
> http://alanstorm.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "PDXPHP" group.
> To post to this group, send email to pdx...@googlegroups.com.
> To unsubscribe from this group, send email to
> pdxphp+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pdxphp?hl=en.
>
--
Interesting. I (obviously) did not know that. Had blithely assumed
that going from 2.9 => 3.0 would be more of a fundamental architecture
change than going from 2.8 to 2.9.
Probably best not to assume anything regarding version numbers, of
course; we've had challenges in that area, since we are committed to
keeping our main version number as part of our name. Much like OS X,
this leads to all sorts of confusion when trying to convince someone
that what they think is a point release update (5.3 to 5.4) is
actually a major version upgrade.
Thanks for your time and the post.
best,
Andrew