Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59662
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F8461F0.2090709@sugarcrm.com>
References: <CAPmfwEnMypV6DFRnRsnCvj+KQk1JG54TX3r1DNHQO3QQ0f+hjA@mail.gmail.com>
	<4F8461F0.2090709@sugarcrm.com>
Date: Tue, 10 Apr 2012 10:59:50 -0700
Message-ID: <CAKOpQSynrt7G=LC2U3BW+f41zS4pXth-o=zHmRXQ58yj7UbPPg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Adir Kuhn <adirkuhn@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30780c089e2b8504bd56e3fa
Subject: Re: [PHP-DEV] [off] PHP: a fractal of bad design
From: kris.craig@gmail.com (Kris Craig)

--20cf30780c089e2b8504bd56e3fa
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Apr 10, 2012 at 9:38 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> Hi!
>
> > today I read this post, I think that some points are valid, follow the
> link for
> > you guys
> >
>
> Could you name a few and explain why you think they are valid and what
> you propose to do to fix them? This article is huge and if you want to
> start a discussion that makes sense (as opposed to a rant which is, I am
> sure, very therapeutic for the author of the post but I'm not sure why
> should we care) I think the approach of "read the whole thing and guess
> what I meant by 'some points'" is not the best one.
>

+1


> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Do you know why a full 1/3 of the internet uses PHP?  BECAUSE IT WORKS!!
It is easy for newcomers and veterans alike.  It's very forgiving when it
comes to typing and other semantics.  As far as an error stack goes, PHP
really doesn't *need* once IMHO because the error messages are already
surprisingly precise (with a few notable exceptions lol), typically telling
you not just what the error is but exactly *where* it is, right down to the
line number!  Personally, I think that's just fucking awesome.

I started programming at the age of 12 using GW BASIC on my old 286 (I
remember how excited I was when my brother managed to obtain a pirated copy
of QuickBASIC lol).  I later "matured" into C/C++.  I didn't start using
PHP until I was 19 or 20.  It's been my favorite language to work in ever
since.  It always amuses me when PERL developers go on their little
soapboxes about how "real" programmers all think PHP is stupid lol.

Granted, PHP has MANY flaws, some of which are accurately mentioned in the
article (though as Pierre pointed out, it doesn't actually raise any new
points; and yes I did read the whole thing, including the comments).  There
are some things that PERL and "Ruby with [sic?!] Rails" do better.  But
that's why we're here.  Instead of trying to use the Internals list to
boost the SEO of your blog, why not actually contribute to make the
language better?  Or do you prefer to just be an armchair quarterback?

--Kris

--20cf30780c089e2b8504bd56e3fa--