Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64850
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.173 as permitted sender)
Message-ID: <50EFB89B.5080202@sugarcrm.com>
Date: Thu, 10 Jan 2013 23:00:43 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: dukeofgaming <dukeofgaming@gmail.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <CAAyV7nEWD7SYjjN_kia9rSknjL2BKi157G1r5VJPfTkHB4Y5ww@mail.gmail.com> <50EDBEA5.1050201@sugarcrm.com> <CAAyV7nHoMwM=Ge8+97mmUiNR1+ChCq3mW+Dgx0r9Hc=yn6Q8=w@mail.gmail.com> <50EE5DAF.2080901@sugarcrm.com> <CAAyV7nFG++8WNpyCk1gByVk3aLSh7CzR1F0fmn2M43thXZQKKQ@mail.gmail.com> <50EF2195.3080907@sugarcrm.com> <CAAyV7nE27JqMEBSd_0b0QYk1OjErHyR_PpvZoBD-fVdAPuDNTQ@mail.gmail.com> <CANVTSm5afTqJuYCm+q2Qb2vzyWYQxJuYRwsZW++RRdbbLZNXBA@mail.gmail.com> <50EF49AF.9050801@b1-systems.de> <48412E0A-3FCC-440D-8479-39B666EB7213@gmail.com> <CAFt2z-m9p0+=ryazD+b779AojdvKCiG3uSBEuLcTuw_1WxJCSQ@mail.gmail.com>
In-Reply-To: <CAFt2z-m9p0+=ryazD+b779AojdvKCiG3uSBEuLcTuw_1WxJCSQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Was Reflection annotations reader - We Need A Vision
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> I have a question, maybe it is dumb: why not those opposed to using
> annotations just... refrain from using them?

We've been there before. You seem to be thinking as a person who only
writes software for himself and has to deal with software only written
by you. However, not everybody has such luxury. Once you start dealing
with bigger projects, language environment and language ecosystem starts
to matter, complexity of the code and complexity of what is being done
with the code starts to matter. If some code is too complex to be
properly understood, it will contain hard to find bugs, it will be
misused, it will be routed around in weird ways due to the fact people
don't understand how it works, and in general it will be a pain to all
around. Basically, it will be a piece of closed source in an open-source
project. And people will hate us for imposing this onto them.
So while "don't use it" may work with isolated features (nobody objects
to mongodb extension because they don't use mongodb), for language
features it does not work. Once it is in, you're stuck with it as a part
of your ecosystem. And since PHP has deep BC traditions, you are stuck
with it next to forever.

> Also, to maybe put things in better perspective and discourage visceral
> vote (because the topic will keep arising until the end of times, I'd bank
> on that) why not make a list of pros and cons to adding this to the
> language?

Did you read the past discussions about the topic? There was a lot of
argument outlined about pros and cons.

> Finally, I remember the lack of support for development has been a
> problem... so why not call out for support to the community?, from GSoC to
> PHP gurus litterate on Comp Sci and software engineering and architecture?

Please note that whoever you call out for will have to support this for
years to come. You probably can write an extension and then just drop it
out there and move on and let others deal with support. Even then
doesn't work that well but at least with extension the problem won't be
acute and will be localized. But with language core part you need
commitment for at least several years, otherwise it would just be piece
of buggy and clunky code that nobody can touch.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227