Originally posted by psychoticmeow
View Post
Announcement
Collapse
No announcement yet.
PHP5's Successor Might Be PHP7
Collapse
X
-
-
Originally posted by Luke_Wolf View Postyes because I should use a hack to get around broken behavior. Have you ever heard the phrase "Don't Live with Broken Windows"? PHP apparently hasn't or this (and many other things) would have been fixed a long time ago instead of adding a new operator as a hack around. There's a reason I avoid this language when I can.
Comment
-
Originally posted by psychoticmeow View PostI think it's amusing that you think this is a serious problem.Last edited by Luke_Wolf; 22 July 2014, 08:08 PM.
Comment
-
Originally posted by Luke_Wolf View PostLiving with broken windows is a serious problem, it promotes duct tape fixes as opposed to properly engineered solutions creating technical debt. Duct tape ends up layering on top of duct tape until you've finally accumulated enough technical debt that you need to completely throw out and rethink the fundamental design of the system. Worse is when you have other systems reliant upon the duct taped system as the technical debt then spreads like the disease it is and it becomes that much harder and that much more expensive to remove the debt from the system even though you eventually will be forced to do so.
Comment
-
Originally posted by psychoticmeow View PostWhat a bunch of meaningless nonsense. The problem here is your understanding of the operator, not the operator itself.
Comment
-
Originally posted by Luke_Wolf View PostNo it's with the operator itself which is why just like Javascript there's a giant "Do Not Use" sign on it and they came up with the ===, operator (much like javascript). I'm sorry but if you can't see the problem with this and the other technical debt issues, and indeed the very problem with living with broken windows then you are very much beyond help and there's no point wasting my breath further on you.
Comment
-
Originally posted by bison View PostI really think Perl developers need to do something like this -- just admit that they bit off too much and take another run at it.
Originally posted by TheOne View PostIt seems that people here talking bullcrap about the language havent played with it since version 4. Please inform your selfs before... the language now even supports namespaces, closures, generators, etc... pretty up to date for me. Theres even a framework for async stuff like nodejs named reactphp. Also hhvm has evolved the language with scalar type hinting and class templates. At leasr scalar type hinting is going to make it into php 5.7. In any case I agree with othe poster that next release should just be 5.7 and 7.0 when they add jit to phpng which is the 5.7 branch
Comment
-
Originally posted by psychoticmeow View PostIf you know you don't want the "broken" behaviour just use the === operator? Seems to work for everyone else.
Still, as far as I know PHP is still really quite slow so it makes me wonder why this is even an issue in the first place. Not saying hat it doesn't serve it's purpose, just that there are other languages with less of these 'gotchas' that can do the same thing and faster.
Comment
-
Originally posted by Tom B View Post'0' and 0 are equivalent
'0' and 'foo' are not equivalent
so logically 0 and 'foo' are not equivalent... except in PHP they bizarrely are. 0 == 'foo'. *scratches head*
Problems which don't have much to do with "PHP is shitty language" and have more root cause in "I can't design a decent and secure code path that doesn't look like stolen straight out of the asylium".
Things like "input validation" do exist for a reason.
Comment
Comment