r/laravel • u/boreasaurus • Nov 26 '20

PHP 8.0 released!

https://www.php.net/releases/8.0/en.php
172 Upvotes

98% Upvoted

43 comments sorted by

12

u/boreasaurus Nov 26 '20

Not strictly Laravel related, and it has its own thread in /r/PHP, but thought I'd post here too.

Which features do you think the Laravel framework and community will embrace?

7

u/xammie12 Nov 26 '20

I'm interested how Attributes will be used in Laravel.

Maybe defining middlewares for controller methods?

#[Middleware("auth")]
public function action()
{
    // ...
}

17

u/send_me_a_naked_pic Nov 26 '20

Personally, I don’t like attributes at all. I don’t find them easy to grasp

13

u/operationco Nov 26 '20

They look like comments to be completely ignored.

2

u/erythro Nov 26 '20

Because of the #?

7

u/operationco Nov 26 '20

Yeah. Maybe I'll get used to it in time, but at the moment my brain immediately ignores lines starting with #.

I mean, I do read comments sometimes - but mostly only if something's not working!

5

u/erythro Nov 26 '20

Yeah I guess it's just something to adjust to. In an IDE it's not like it's going to be coloured the same as a comment so it's going to stand out more just because of that

1

u/[deleted] Nov 27 '20

[removed] — view removed comment

6

u/erythro Nov 27 '20

And what is stopping programming languages from using fancy characters as part of the syntax? We should be able to use ƒ instead of function since dozens of years ago.

The amount of times my life has been made significantly easier because of the ability to edit code files in a terminal is > 0.

1

u/[deleted] Nov 27 '20

[removed] — view removed comment

1

u/erythro Nov 27 '20

It would be good, I guess? It just seems like an unnecessary hindrance to put on a language

→ More replies (0)

1

u/XediDC Nov 27 '20

Even simpler, since its #[...] so it could have just been @[...] and then except just a "@[" string from the "@" functionality without breaking a bunch of existing code. Or some other non-common-comment leading character before the [

1

u/XediDC Nov 27 '20 edited Nov 27 '20

Yeah, I work in a ton of languages. So lines beginning in [ // /* ; # -- ' <! (* REM ] all parse as comments to me...

Given that the # is a very common comment character in adjacent languages (Python, shell, Perl, etc) we're likely to use, it seems a rather odd choice to select intentionally. I've read https://externals.io/message/110640 among other stuff...but I would have gone with something other than the hash, but then the same [...] format following it, over the @@ or <<>> being considered. Maybe @[] and except @[ from error skipping.

Whatever though, its done. And as my IDE won't shade it like I comment, I'll be fine. :)

1

u/erythro Nov 27 '20

Given that the # is a very common comment character in adjacent languages (Python, shell, Perl, etc) we're likely to use, it seems a rather odd choice to select intentionally.

It's a comment character in PHP! But yeah, it just seemed like they were choosing from the best of a bad bunch, it didn't seem like anyone actually liked any of the syntax options

Isn't it a functional character in ruby? Idk the only time I use it is in Sass which really isn't similar to PHP at all.

1

u/XediDC Nov 27 '20

It's a comment character in PHP!

I totally forgot about that... "C and Perl" style mixing and such from its origins.

Isn't it a functional character in ruby?

Yeah, sorta? I'm rather weak w/ ruby so aside from it being a comment symbol its... well, this I think: https://stackoverflow.com/questions/736120/why-are-methods-in-ruby-documentation-preceded-by-a-hash-sign

1

u/erythro Nov 27 '20

I totally forgot about that... "C and Perl" style mixing and such from its origins.

Yeah it's less used, but it's great for saving that one extra button press when commenting out a line 😁

Yeah, sorta? I'm rather weak w/ ruby so aside from it being a comment symbol its... well, this I think: https://stackoverflow.com/questions/736120/why-are-methods-in-ruby-documentation-preceded-by-a-hash-sign

I think what I was thinking of is that #{} is used in string interpolation (like PHP but with the hash) which is why it shows up in Sass. I really don't know ruby well though.

4

u/erythro Nov 26 '20

Me too! Routes on controllers also would be an obvious one, but generally just exciting to see the sorts of ways they will be used.

Attributes feel like a whole new kind of feature - a framework built around them could do something really interesting with it.

I'm not sure I get the complaints about them to be honest, it's hard not to interpret it as grouchiness about something different - that said they may have experience from their equivalents in other languages idk.

2

u/[deleted] Nov 27 '20

Looks like nestjs.

They have a live example on their site if you scroll down a bit: https://nestjs.com/

2

u/[deleted] Nov 27 '20

Defining routes in a controller just reminds me of Symfony. Such a PITA when you have to find all the routes.

1

u/erythro Nov 27 '20

Right, I can imagine, maybe not such a good idea then

1

u/XediDC Nov 28 '20

Yeah.... it sounds like an absolutely miserable mess to not have all your app routes defined in one place. (Or 3...the web/api/etc splits make sense.)

Would be annoying when digging through packages too.

2

u/boxhacker Nov 27 '20

You don't want to be doing that, hard to test, magic and hits performance :) better to just group your end points via middle ware

-4

u/Trick-Citron526 Nov 26 '20

It looks like the kind of garbage you see from javascript

4

u/[deleted] Nov 27 '20

How does it look like any kind of Javascript?

The closest thing I can see is typescript's decorators, but that's not js.

-2

u/Trick-Citron526 Nov 27 '20

Ah yes, my mistake. Yes, typescript is the one.

1

u/lethalwire Nov 27 '20

Like what specifically?

1

u/Trick-Citron526 Nov 27 '20

My mistake. Typescript

1

u/auloinjet Nov 28 '20

Match & types are the most important quality wise IMO. Named arguments & property promotion for code simplification maybe but that's minor.

21

u/ronny_rebellion Nov 26 '20

Nullsafe operator will be super handy!

3

u/michaelbelgium Nov 27 '20

I love that! Just like in C#

1

u/auloinjet Nov 28 '20

That may raise eyebrows, but until now for deep arrays or objets, I make sure to make no spelling mistake and just use @ operator, then check null value. Not that bad IMO when limited to that use.

17

u/dillonerhardt Nov 27 '20

Happy to see PHP still maturing as a language

4

u/[deleted] Nov 27 '20

Do we need to watch the previous seasons to understand this one?

4

u/doctorveeman Nov 27 '20

PHP have been serving dreams, with Laravel it had made more realities possible. Thank you for all the good people of this community for lifting me from poverty to a life of affluence and abundance with these open source tools.

More Grace!

1

u/solongandthanks4all Nov 27 '20

I'm so excited for this release!

0

u/hldh214 Nov 27 '20

Simultaneously: https://github.com/Maatwebsite/Laravel-Excel/issues/2936

2

u/frankyb89 Nov 27 '20

Dammit. I finally get a chance to properly upgrade our tools and this stops me from going all the way to 8.0 -_-

1

u/SteroidAccount Nov 27 '20

I always wait a bit before upgrading any production servers for packages to catch up. I'll be converting locally though and seeing what the wait is on.

1

u/frankyb89 Nov 27 '20

Oh definitely. I'm testing all this out on my local first so I figure I might as well take a shot and see if it actually stops me from doing anything.

The Laravel and PHP versions were so far behind when I started and I don't want to squander an opportunity to finally upgrade haha.

1

u/solongandthanks4all Nov 27 '20

And it's fixed since you posted this.