From PHP 5.6 to PHP 8.2

[@ahmedyoussef7923]

PHP getting better every new version . Thank you very much ❤

[@Apocalyarts]

Wow, very nice and a super compact rundown, thx!

[@nunomaduro]

Thank you!

[@waltermelo1033]

that thumb reflect my thoughts. I'm really considering migrate from JS to PHP too...

[@nunomaduro]

Try Laravel.

[@FreddieOmega]

awesome explanations!

[@nunomaduro]

Thank you!

[@coder_one]

Certainly, to check whether you can override the variable $name marked as "readonly" or placed in the "readonly" class, you still need to run this code. That's how PHP works... You find out about existing errors in the code from clients using the production application ;)

[@spicynoodle7419]

PHPstan will help with this

[@TheRafark]

This would be caught when unit testing. If this is caught in production it means you don’t test your code, which is wild

[@phpannotated]

❤ PHP

[@it-s-me-mohit]

Great video nuno. I had one question. I have a legacy PHP application version 5.4 using zend, symfony, restler rtc. Wanted to upgrade it to the latest version. Is it better to rewrite it from scratch in a new framework like laravel or migrate everything and stay on the same frameworks

[@jadidlar4765]

thank you for your video

[@nunomaduro]

You welcome!

[@DeTechDivus]

Would've been nice if we could remove empty {} as well

[@GAoctavio]

I think proper standard engine support for async, futures, coroutines and threading is due

[@maxymajzr]

What would you use threading for? I'm interested to know what you have going on as challenge with which threading helps.

[@GAoctavio]

@@maxymajzr I'm currently generating loads of PDFs in parallel with Dompdf, the only way of not stalling the request for 15 minutes its to use Laravel Jobs but thats an architectural mess IMO (not very elegant to have an external program as supervisor, I found it breaks very often, doesn't reload the configuration properly, etc). In the end I replaced it with proc_open with correct command arguments to run the proper job, marshalling job data into the database as JSON. It would be trivial with a Thread Pool implementation, but I'd need to recompile the PHP interpreter and I don't know how fiddly the support is. Proper implementation and testing would take me a lot of time

[@jmon24ify]

Have you tried reactphp?

[@GAoctavio]

@jmon24ify Looks interesting but I don't how useful it would be with my problem since Dompdf doesn't really block aside from when writing to disk once it has processed everything and I'd have to write a new service to even begin to try

[@winfle]

@@GAoctavioyou can use pthreads, But generally I recommend to use something like Golang for heavy workload and offloading these parts.

[@mmahgoub]

TypeScript is that you?

[@LeoSpabo]

What is the ABC app in the Menubar?

[@spicynoodle7419]

You sbould have showed off the algebraic types like string|null or Arryable&Responsable

[@nunomaduro]

Yeah - but wanted keep the example simple.

[@silva-dsd]

Great video Nuno 👏. Hopes PHP never ceased to improve and evolve. PHP should provide an easy and smooth transition for developers. What tool you used to change php version easily, using mac?

[@nunomaduro]

brew.sh/

[@silva-dsd]

@@nunomaduro Yes, I have been using it, however sometimes changes require a restart. Thanks anyway.

[@lucasj.pereira4912]

Now we only need the constructor to make the "{ }" optional because a lot of times it is just empty. Like we have in interfaces: public function __constructor (public string $name);

[@DrYouz]

What is your font used in your IDE please ?

[@DrYouz]

You like but you tell me :)

[@DrYouz]

?

[@brandon26]

Do you know of any performance improvements in this new versión?

[@SaiyanJin85]

The only thing that is missing is typed arrays.

[@nunomaduro]

With PHPStan, we support those.

[@jamesrosemary2932]

Sitll waiting for setters and getters.

[@dominiq6864]

I really like the direction PHP is developed in recent years. But unfortunately, it still sucks (and sadly will suck forever). It still has: - The infamous inconsistent argument ordering: strpos($haystack, $needle, $offset) and array_search($needle, $haystack, $strict) - facepalm 🤦‍♂ - Lack of proper module system - importing all files to the global scope and bothering with complex namespaces is a nightmare - Awful ancient "

[@8LynX8]

You are right BUT: - Inconsistent argument ordering - YES, but it is not a big deal, when you are using modern IDE - Lack of proper module. Not sure what you mean, but it is solved by composer autoloader. Basically it is must have - "

[@dominiq6864]

@@8LynX8 yeah, well I think backward compatibility causes most flaws of PHP, unfortunately 😅 I really hope they will eventually introduce more consistent APIs in future releases and deprecate old ones - then PHP would probably be one of the best server-side languages for backend devs

[@b0janix]

I agree about the inconsistencies in the argument ordering, but since PHP 8 you have this thing called named arguments. So you just need to know the name of the argument passed to that function and you can place the arg anywhere in the param signature

[@dominiq6864]

@@b0janix yeah, named arguments help a lot and I must admit that other languages should implement this feature as well (but this doesn't justify previous PHP's bad design decisions) Nevertheless I wish PHP will fix some of its flaws in future versions, maybe it is going to be great some day ;)

[@GamePlayByFaks]

seems you haven't used composer 2 and php 8.2 and some recent framework like laravel or symfony, about 90% of your issues are solved. add phpstan level 10 and strict type on top and you will never have any major issues in general.

[@mateussantana4418]

PHP became a great and robust programming language! What a shame it's dying 😆

[@nunomaduro]

It's not dying. 👍🏻

[@mateussantana4418]

@@nunomaduro it was a joke 😄

[@levyroth]

It was never great, and it will never be. Let it die.

[@nunomaduro]

@@levyroth Over my dead body

[@muhammadawwab4402]

@@levyroth you would die first