Question is it worth if to release a new major version of a package that still target #PHP8.1 since PHP8.2 will soon enter security fix only ?

Gestern die nächsten möglichen Schritte zum #OpenSource #CMS #CONTENIDO besprochen.

Wir werden das Release der 4.10.2-dev vorbereiten.

Auch suchen wir noch Tester, die den aktuellen develop-Branch auf Herz und Nieren unter #PHP8 testen.

Lust? Zeit?

#developer #development

https://github.com/CONTENIDO/CONTENIDO

So, i learned today that #PHP #php8 has deprecated strftime and #php9 plans to remove it. They officially say you should be using either date() or the intldateformatter suite instead.

Like... what?

strftime is ISO Standard! It's literally POSIX! The format flags are even "printf"-style!

Not only that, but the proposed """replacements""" force you to choose between whatever variant of racism, classism and Americentrism you like!: date() works only in US English and only for numbers, whereas intldateformatter supports languages but requires users of any culture other than "US English" to load a whole PHP module.

Oh, besides you have to change the format strings (woe betide if you are using user-provided!), ALSO these replacements *invert the logic* for processing the format strings as well: intldateformatter etc escapes everything that is *not* a format flag.

Fortunately, forwardports already exist such as https://github.com/alphp/strftime/ .

After some thoughts on the matter I've decided to do nothing about the #CSV deprecation in #PHP8.4 with league/csv here's why
https://nyamsprod.com/blog/csv-and-php8-4/

@Girgias I believe in french we say ... passer la patate chaude

Working on the #doctrineorm v1 codebase and its test suite, make you realise how much work has been done on #phpunit, and it simply works! Thank you @sebastian!

At the same time the legacy Doctrine v1 still manages OK-ish in the era of #php8 ! Still with no class namespaces and by implementing its own autoloading system! Is it probably from #php4 times?

Kudos to the original authors!
(Are they around here BTW?)

NEW RELEASE!

Fixer v3.55 brings brand new `ordered_attributes` rule that extends our support for #PHP8 . There are also multiple internal improvements, as we bumped #PHPStan level to 7 and fixed several reported issues.

https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/releases/tag/v3.55.0

#php8 rocks

Is the #php8 logo meant to be a mobius strip?

Either way I do like it.

There is a high bar for #php9

Another release, my another 8 contributions . This time my changes are mostly related to DX and processes in general. But there's also one new feature: support for #PHP8 attributes in `method_argument_space` rule .

Happy fixing!

https://phpc.social/@PHPCSFixer/110977877059389775

Und zack, da ist es, wieso ich so ein komisches Gefühl hatte.
Ein weiterer Kunde mit #Wordpress und #PHP8 Problem. Alles mal durchdenken und Angebot ist raus.
Nur die Zeit drängt, da er bei IONOS ist und die stellen ab April um.
Ansonsten 8 EUR mehr fürs Hosting.

I updated #typo3scan cli tool for #TYPO3 v12 and #php8. It delivers the same results as the 'ExtensionScanner' in the backend. You can use it to check extensions, if you have not v12 running or the extensions break the backend.

https://github.com/mschwemer/typo3scan

(PRs pending)

In-depth analysis of the new features brought by PHP 8 related to arrays, variables, operators, and exception handling.

Deepak Vohra also discusses some trait-, class-, and function-related features.

#InfoQ article: http://bit.ly/40RjUB3

Ok, this might be a bit of a niche one but I'm massively stuck and could do with some help.

Any #php devs out there that are using #pdo_sqlsrv on #php8 on an Apple Silicon machine?

I keep getting an error `Unsupported processor architecture.`. The strange thing is that this works on our current dev environment on the #php7 branch

Yesss.. Update PHP7.3 auf #PHP8 nun geglückt. Bei #Strato für Kunden läuft nun WP6.1.1 läuft sauber incl. aller Plugins und dem Theme.
#wordpress
*Schulterklopf, man hab ich geschwitzt eben.