66 karma · joined October 6, 2015
Many companies have dumb policies. They are the ones that need to change.
That's the sort of thinking we'd benefit from having less. Legacy is a terrible burden.
http://php.net/manual/en/language.types.type-juggling.php
How would you fix this without breaking most PHP code out there?
How would you fix ==, > and < behaviour without breaking most PHP code out there?
How would you fix Unicode without breaking most PHP code out there?
If PHP fixed things like this, it would be a decent programming language, but it would also break a lot of things. Kinda of like what python3 did, only that it didn't have to break quite so much, since python2 was already pretty decent.
Php7 did nothing like that, that's why the "porting" process was so light. But it also means it didn't fix any of the big things.
How exactly?
Because your question is loaded?
Why is
Post::belonging_to(usre).load(&connection)
an improvement over SELECT * FROM posts WHERE usre_id = 1;
?... to which the answer is probably more obvious.
Seriously though, this is "Handling 1B connections in a week with Varnish".
- In the modern world, people are afraid of XML
- 95% of people still don't understand XML namespaces
I guess that's one way of saying that something is too complicated :)Without changes to the code? Has there even been a language where that has been true?
That's a rather amazing quip. How would I, in my mid-thirties, accidentally write a buffer overflow in Haskell or Rust?
What would be the reason to do that?