An Exceptional Change in PHP 7.0 • Hacker News Board

Re: An Exceptional Change in PHP 7.0

#51

Post by debacle » Tue, Oct 06, 2015, 2:25 PM UTC

sarciszewski wrote: post #50

debacle wrote: post #49

Earlier quoted context omitted.

We need more BC breaks, not fewer. I'd really like to see a lot of functions that return FALSE on failure throw exceptions in the future. We could also tidy up the stdlib a bit and give primatives some OO love. If you're going to break BC, might as well do it right.

So, onwards to PHP (gr)8?

I'm hoping Hack can liberate us.

Re: An Exceptional Change in PHP 7.0

#52

Post by kazinator » Tue, Oct 06, 2015, 4:32 PM UTC

sarciszewski wrote: post #43

deckar01 wrote: post #42

Earlier quoted context omitted.

I have to use PHP every day and I rarely go a day without complaining about it.

You're the exception, not the rule. I mostly hear C/C++, Ruby, Python, etc. devs complain about PHP. Very rarely actual PHP developers. And typically, their complaints are less of the moan-ass "waaah, they use a \ for namespace separation" and more "ugh, why don't they disabled emulated prepared statements by default"? Only one side is constructive.

None of those who are complaining about the monument of shit being erected outside of town is actually an erector of monuments made of shit.

Typically, their complaints are about the ugly appearance and smell.

Only one side is constructive.

Re: An Exceptional Change in PHP 7.0

#53

Post by durrrrrrr » Tue, Oct 06, 2015, 11:35 PM UTC

betenoire wrote: post #28

durrrrrrr wrote: post #26

Earlier quoted context omitted.

Same thing as before, you've stated it's ugly, but haven't given any specific examples of why you think this.

do we really need to see bad java examples to understand his opinion?

Yes. Just some general points or examples.