2,166 karma · joined May 15, 2014
Email: theodorejb@gmail.com Website: https://theodorejb.me
Edit: I'm referring to building the framework itself (e.g. to contribute a fix). Building an Angular project with the CLI works quite well.
Maybe I'm misunderstanding you, but it sounds like you're saying that speed doesn't matter when responding to HTTP requests. This couldn't be further from the truth. The less time a response takes, the more requests can be handled per second, which is critical for scaling Web services. PHP 7.x handles 2-3 times as many requests per second on the same hardware compared to PHP 5.
Also, I don't agree that PHP is only suitable for responding to network requests. I've also found it ideal for writing CLI programs which can run on a schedule and share logic with HTTP APIs.
> We will also publish the IE11 upgrade through Windows Update and Windows Server Update Services (WSUS) for all versions of Windows Server 2012 and Windows Embedded 8 Standard later this year.
Nice! I wonder, will they eventually do this with their Chromium-based version of Edge?
* Trailing commas in function/method calls
* array_push() and array_unshift() can now be called with a single argument (helpful when using the spread operator)
* TypeError now reports wrong types as int and bool instead of integer and boolean (no more "Argument must be an instance of integer, integer given" errors)
* Deprecation of case-insensitive constants
* json_decode() and json_encode() now support a JSON_THROW_ON_ERROR flag (removing the need to call json_last_error() to see if an error occurred)
* setcookie() now accepts an associative array of options, and supports the samesite attribute
* More flexible heredoc syntax
- Unquoted strings
- The __autoload() method
- The track_errors ini setting and $php_errormsg variable
- create_function()
- each()
- The $errcontext argument
Numerous internal optimizations and language improvements will become possible in PHP 8 when these features are removed.
Furthermore, because you have to rely on third-party libraries for all the features that React doesn't provide, you have to worry about separately keeping them all up-to-date. What if there's a critical bug fix in the latest version of your HTTP library, but it's only compatible with the latest version of React, which isn't compatible with the router version you're using? In my experience it takes a lot more time to keep dependencies up-to-date and working together with React than with Angular.
http://webcache.googleusercontent.com/search?q=cache%3Ahttp%...