For any kind of depreciations, there is always an alternative. The reason why things get deprecated and then get removed is because a lot of the features that gets deprecated are unsafe to use or too old and obsolete.
I mean many fair points presented -- howwwweeever haha.. For all the breaking changes PHP has made since the 5.6 days, we haven't got the sort of tradeoffs that would justify them at minor versions. Feature priority is quite mysterious.. for instance the many, many, many times hopes have been dashed with RFCs attempting to bring in operator overloading, objects as keys and proper type casting. Originally coming from other languages; I strongly think these three features should have been top priority long before any of the PSR, traits or attributes were thought of. Nothing drives me to consider porting projects more than these. That, and I surely wish PHP deprecation habits were more along the lines of the Khronos group's. Perhaps alternatively if it were just more predictable; such as at X.5 versions, function signature changes may occur and at X.7 versions type changes may occur. Anything more systematic would be handy.
It would be nice if there was a separate alert system. One thing you can do is $catch_deprecated = function( int $error_code, string $message, string $offending_file, int $offending_line, array $active_variables ){ $DebugMode=false; static $caught = [ ]; $alert_dir = '/srv/myproject/alerts/'.$error_code .'/'; $log_dir = '/srv/myproject/log/'.$error_code .'/'; if( $DebugMode ){ file_put_contents( $log_dir . 'deprecated.log', PHP_EOL.$message.PHP_EOL, , FILE_APPEND | LOCK_EX); } if( empty( $caught[ $message ] ) ){ $caught[ $message ] = true; touch( $alert_dir . 'DEPRECATED-' . $message ); } }; set_error_handler( callback: $catch_deprecated, error_levels: E_DEPRECATED ); With this, or something very close, you end up with only a single file per error thrown unless you activate debug mode to see the full error output.
Not if companies start to realize that php changes can cost too much money and time. I was ok with php until it made my website useless for 20 days after an update to php 7.4.
From the developpers' point of view changes may be great, but they are terrible for business. A language update should not break applications, but that's exactly what PHP is doing at the moment. I'm a developper and a businessman and I will never use PHP in my projects again.
For any kind of depreciations, there is always an alternative. The reason why things get deprecated and then get removed is because a lot of the features that gets deprecated are unsafe to use or too old and obsolete.
I thought deprecations and notices were distinct things, at least when it came to error reporting?
I mean many fair points presented -- howwwweeever haha.. For all the breaking changes PHP has made since the 5.6 days, we haven't got the sort of tradeoffs that would justify them at minor versions.
Feature priority is quite mysterious.. for instance the many, many, many times hopes have been dashed with RFCs attempting to bring in operator overloading, objects as keys and proper type casting. Originally coming from other languages; I strongly think these three features should have been top priority long before any of the PSR, traits or attributes were thought of. Nothing drives me to consider porting projects more than these.
That, and I surely wish PHP deprecation habits were more along the lines of the Khronos group's. Perhaps alternatively if it were just more predictable; such as at X.5 versions, function signature changes may occur and at X.7 versions type changes may occur. Anything more systematic would be handy.
yeah we dont want 1gb error logs, better to disable notices
It would be nice if there was a separate alert system.
One thing you can do is
$catch_deprecated = function(
int $error_code,
string $message,
string $offending_file,
int $offending_line,
array $active_variables
){
$DebugMode=false;
static $caught = [ ];
$alert_dir = '/srv/myproject/alerts/'.$error_code .'/';
$log_dir = '/srv/myproject/log/'.$error_code .'/';
if( $DebugMode ){
file_put_contents( $log_dir . 'deprecated.log', PHP_EOL.$message.PHP_EOL, , FILE_APPEND | LOCK_EX);
}
if( empty( $caught[ $message ] ) ){
$caught[ $message ] = true;
touch( $alert_dir . 'DEPRECATED-' . $message );
}
};
set_error_handler( callback: $catch_deprecated, error_levels: E_DEPRECATED );
With this, or something very close, you end up with only a single file per error thrown unless you activate debug mode to see the full error output.
What chair are you using? 🔥
Well, deprecations = more work for us 😅
Not if companies start to realize that php changes can cost too much money and time. I was ok with php until it made my website useless for 20 days after an update to php 7.4.
I remember a lot of deprecations in WordPress code.
From the developpers' point of view changes may be great, but they are terrible for business. A language update should not break applications, but that's exactly what PHP is doing at the moment. I'm a developper and a businessman and I will never use PHP in my projects again.