Re: [PHP-DEV] [VOTE] Reclassifying engine warnings

This is only part of a thread. view whole thread
  106946
September 12, 2019 13:59 chasepeeler@gmail.com (Chase Peeler)
On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson <oludonsexy@gmail.com> wrote:

> Thanks to those who can vote, all in all I hope for a better language where > we can proudly post jobs(even intern) for on our company's website without > been looked down on as inferior. > > If you're so embarrassed by the language, then why not use something else, instead of trying to force such massive changes on the entire user base?
Also, if you really think this is going to change how non-PHP developers view PHP, you're sorely mistaken. The few I've talked to about this, in order to gauge how the languages they work in handle BC breaks, were appalled that such a major breakage would be forced on users, even though they personally don't like the fact that PHP supports uninitialized variables. Again, I implore everyone to stop trying and make everyone else like us. Our language is awesome because of the fact that it is different and flexible. That flexibility allows you to be strict if you want. If we just want to turn PHP into another language that is like everything else out there, then what's the point of even using PHP to begin with?
> Since I can't vote, I can only hope for the best. > > <3 > > On Thu, Sep 12, 2019, 1:17 PM Nikita Popov ppv@gmail.com> wrote: > > > Hi internals, > > > > I've opened the vote on //wiki.php.net/rfc/engine_warnings. > > > > There are 4 votes, all of them independent. The first 3 are for specific > > cases that were controversial during the discussion, the last one is for > > the remainder of the proposal. > > > > Voting closes 2019-09-26. > > > > Regards, > > Nikita > > >
-- Chase Peeler chasepeeler@gmail.com
  106955
September 12, 2019 14:12 oludonsexy@gmail.com (Olumide Samson)
On Thu, Sep 12, 2019, 2:59 PM Chase Peeler <chasepeeler@gmail.com> wrote:

> > > On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson <oludonsexy@gmail.com> > wrote: > >> Thanks to those who can vote, all in all I hope for a better language >> where >> we can proudly post jobs(even intern) for on our company's website without >> been looked down on as inferior. >> >> If you're so embarrassed by the language, then why not use something > else, instead of trying to force such massive changes on the entire user > base? > Anything considered through vote is opinion based, not the way you could
call "force" and I think you can also ask those who are not embarrassed by the current language situation to stick to whatever is their current version. Upgrading can't be for everyone. Only those who like major features/changes of a new version upgrade.
> > Also, if you really think this is going to change how non-PHP developers > view PHP, you're sorely mistaken. The few I've talked to about this, in > order to gauge how the languages they work in handle BC breaks, were > appalled that such a major breakage would be forced on users, even though > they personally don't like the fact that PHP supports uninitialized > variables. > I'm sure you are the one mistaken here, cos you don't speak for non-PHP
developers likewise I don't. You can in all utmost speak for yourself like I did In my last email.
> > Again, I implore everyone to stop trying and make everyone else like us. > Our language is awesome because of the fact that it is different and > flexible. That flexibility allows you to be strict if you want. If we just > want to turn PHP into another language that is like everything else out > there, then what's the point of even using PHP to begin with? > > I'm sure you are insulting the Project through those written words. If the
project still want to be what it has always been, then there's no want or need for anything called @internals cos the language can actually still stick to PHP 3 and become what it has always been without any updates or changes. Like I said, since I can't vote I can only hope for the best. Since I can't vote, I can only hope for the best.
>> >> <3 >> >> On Thu, Sep 12, 2019, 1:17 PM Nikita Popov ppv@gmail.com> wrote: >> >> > Hi internals, >> > >> > I've opened the vote on //wiki.php.net/rfc/engine_warnings. >> > >> > There are 4 votes, all of them independent. The first 3 are for specific >> > cases that were controversial during the discussion, the last one is for >> > the remainder of the proposal. >> > >> > Voting closes 2019-09-26. >> > >> > Regards, >> > Nikita >> > >> > > > -- > Chase Peeler > chasepeeler@gmail.com >
  106959
September 12, 2019 14:21 chasepeeler@gmail.com (Chase Peeler)
On Thu, Sep 12, 2019 at 10:13 AM Olumide Samson <oludonsexy@gmail.com>
wrote:

> > > On Thu, Sep 12, 2019, 2:59 PM Chase Peeler <chasepeeler@gmail.com> wrote: > >> >> >> On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson <oludonsexy@gmail.com> >> wrote: >> >>> Thanks to those who can vote, all in all I hope for a better language >>> where >>> we can proudly post jobs(even intern) for on our company's website >>> without >>> been looked down on as inferior. >>> >>> If you're so embarrassed by the language, then why not use something >> else, instead of trying to force such massive changes on the entire user >> base? >> > Anything considered through vote is opinion based, not the way you could > call "force" and I think you can also ask those who are not embarrassed by > the current language situation to stick to whatever is their current > version. Upgrading can't be for everyone. > Only those who like major features/changes of a new version upgrade. > I do like new features. There are tons of new features that can be added
without such a massive and unnecessary BC break.
> >> Also, if you really think this is going to change how non-PHP developers >> view PHP, you're sorely mistaken. The few I've talked to about this, in >> order to gauge how the languages they work in handle BC breaks, were >> appalled that such a major breakage would be forced on users, even though >> they personally don't like the fact that PHP supports uninitialized >> variables. >> > I'm sure you are the one mistaken here, cos you don't speak for non-PHP > developers likewise I don't. > > You can in all utmost speak for yourself like I did In my last email. > >> >> I'm not claiming to speak for everyone. I did provide some anecdotal evidence though.
> Again, I implore everyone to stop trying and make everyone else like us. >> Our language is awesome because of the fact that it is different and >> flexible. That flexibility allows you to be strict if you want. If we just >> want to turn PHP into another language that is like everything else out >> there, then what's the point of even using PHP to begin with? >> >> > I'm sure you are insulting the Project through those written words. If the > project still want to be what it has always been, then there's no want or > need for anything called @internals cos the language can actually still > stick to PHP 3 and become what it has always been without any updates or > changes. > > Not an insult at all. PHP has made a lot of awesome improvements, and continues to make more. We can add things like union types, enums, etc.,
without losing the flexibility that makes the language great. This RFC takes away something that, in the opinion of many, makes PHP better than the other options out there.
> Like I said, since I can't vote I can only hope for the best. > > Since I can't vote, I can only hope for the best. >>> >>> <3 >>> >>> On Thu, Sep 12, 2019, 1:17 PM Nikita Popov ppv@gmail.com> wrote: >>> >>> > Hi internals, >>> > >>> > I've opened the vote on //wiki.php.net/rfc/engine_warnings. >>> > >>> > There are 4 votes, all of them independent. The first 3 are for >>> specific >>> > cases that were controversial during the discussion, the last one is >>> for >>> > the remainder of the proposal. >>> > >>> > Voting closes 2019-09-26. >>> > >>> > Regards, >>> > Nikita >>> > >>> >> >> >> -- >> Chase Peeler >> chasepeeler@gmail.com >> >
-- Chase Peeler chasepeeler@gmail.com