Its the start of a new era, and looking promising. Congrats PHP internals.
Oh, I got to check my server
I develop plugins for WordPress. I’ll be able to use PHP 8 in about 2 years.
That’s a weird way to spell 5 years
WP devs still generally can’t safely use PHP7 syntax, WordPress is terribly behind the times. The upcoming WP 5.6 will work with PHP8 and still support PHP5.6!
I’m lucky my clients are generally forward thinking and I was able to completely abandon PHP 5 this year. So at least I can safely use 7.0 syntax. Planning to phase out PHP 7.0-7.2 by the end of Q2 2021.
If we (the developers) don’t push it, people won’t follow.
This is going to be a fun weekend!
Haha chuckles I am in self-inflicted danger
sudo apt-get install php8.0-cgi php8.0-cli php8.0-common php8.0-curl php8.0-fpm php8.0-gd php8.0-mysql php8.0-intl php8.0-mbstring php8.0-memcached php8.0-opcache php8.0-phpdbg php8.0-redis php8.0-soap php8.0-sqlite3 php8.0-xdebug php8.0-xml php8.0-zip
Today we give thanks to Ondrej for putting the latest builds on our table.
hmm
Time to play with the new nullsafe operator.
Won’t it make harder to find bugs previously exposed by “Call to a member function on null” ? I mean, I see the good in this but it can also cause a lot of debugging nightmares.
CTRL+SHIFT+F @todo: ?-> here I go. I’ve waited for this for sooo long.
Yes!
This is going to save me so much code to write!
Any news when a “php:8.0-fpm” docker image will be available?
Soon PornHub get a PHP 8 update.
JIT porn
Members
Online