Nikita Popov / What’s new in PHP 8.0? [eng]

[@rodelias9378]

Nice talk. Thanks a lot, Nikita, for all your amazing work with PHP.

[@karol.sobanski]

19:58 this is not a minor feature! This soooo convinient, when you now actually don't have to commit additional meaningless line to each change you make on your parameters. Thank you!

[@eugenesidelnyk4600]

What soft do you use to create presentations?

[@serhiicho]

@@User('string') seems nicer than But it's all preferences, whatever these guys decide we will not complain Big Thanks to Nikita for his priceless work for open source

[@maxicx75v]

One of these may be significantly harder to implement than the other.

[@johnrcornell]

First they pick a horrible namespace separator based on a rushed 5-minute IRC conversation and now this hideous attribute syntax. It’s like they’re actively trying to ruin the aesthetics of the language as much as possible. Does the core team not realize that people have to stare at this stuff all day?

[@fixmedev521]

Спасибо

[@nasragiel]

The "something or false" "Pattern" should be removed, not supported... :(

[@maxicx75v]

I agree that it's bad coding, but there are built-ins and lots of custom code out there that do that. Removing it would be a BC break.

[@nasragiel]

@@maxicx75v it's a major version it would be totally OK and IMHO urgently needed to get rid of the past mistakes. Best solution would be to provide consistent named classes for all the old stuff or even better create proper classes to deal with strings or arrays for example and keep the mistakes. However, I would prefer to get the API cleaned up.

[@angeljo6020]

can we recover from fatal errors?

[@buggaman2009]

Anyway to make php asynchronous

[@iamise]

swoole

[@eugenesidelnyk4600]

It would be a great thing to implement variadic return type. For example, if we had such function: _function calculateResult(): int_ _{_ _return 123;_ _}_ And we want to extend functionality and return some additional information without breaking working code: _function calculateResult(): int..._ _{_ _return 123, 256; // or ...[123, 256]_ _}_ Thus, when we call _calculateResult()_ : _$a = calculateResult(); // 123_ _$a, $b = calculateReult(); // a = 123, b = 256_ And also look at medium.com/@liamhammett/php-wishlist-typing-9f16851c0258 especially where return arrays.

[@kristun216]

Can't you already do this?

[@eugenesidelnyk4600]

@@kristun216 i don't think so

[@kristun216]

@@eugenesidelnyk4600 iirc when you return an array you can deconstruct it as an array in the return variable. function foo(){ return [123, 456]; } [$a, $b] = foo(); // a = 123, b = 456 It's not as pretty as in python or JS but it works

[@eugenesidelnyk4600]

@@kristun216 i know this, but yeah, if there are dozens of code expecting one value returned, but we have to return also another, all these places have to be changed

[@roman-romadin]

Thank you. Please, say what soft do you use record video.

[@ALZlper]

Try OBS

[@Cognitoman]

I like php, but there is a lot weird ways of doing things, and unconsisted built it function . I hate how booleans return 0 and 1s... null value shows ups empty string when printed, the arguments for built in functions order of parameters changes as well as naming convention. I hate how doing callbacks looks dirty.

[@AbhinavKulshreshtha]

See "25 years of PHP by Rasmus Lerdorf", He explains the logic behind these what we call inconsistency, With named parameter, these should now not be problem anymore.

[@kasedsoftsilicon3268]

Thank you for knowledge so good i like this video from the PHP 8

[@djanthony6662]

You are legend.

[@ando-]

If you are here for infos about generics head over to 44:43

[@Cognitoman]

Php never will get generics lol

[@arunabraham9382]

@@Cognitoman Even go dont have generics

[@Cognitoman]

@@arunabraham9382 yeah thats not good

[@razt3757]

24:56 fucking finally ffs

[@paulmimicry9147]

its like java beans ahhaha or java annotations :D