Live data from Hacker News

PHP 8.1.0

php.net

81–90 of 286 posts

Re: PHP 8.1.0

#81
post #7

Fibers "allow blocking and non-blocking implementations to share the same API" That's an interesting contrast to Python where the need to use "value = await fn()" v.s. "value = fn()" depending on whether or not that function is awaitable causes all kinds of API design complexity, all the way up to the existence of tools like https://github.com/python-trio/unasync which can code-generate the non-async version of a lib…

> allow blocking and non-blocking implementations to share the same API

Sounds like an excellent way to create weird concurrency heisenbugs.

Re: PHP 8.1.0

#83

Earlier quoted context omitted.

With a proper type system you don’t need to run your code 50 times a minute.

As someone who isn't perfect, it's nice to be able to quickly iterate on ideas.

Iterating on ideas is much quicker when the compiler tells you when you made a mistake or failed to change your code after changing your mind.

Re: PHP 8.1.0

#84

I've been using PHP since 5.x. Often had to work on older 4.x web apps. I find it interesting when I read people saying "PHP has come a long way. It's a proper language now, etc." If you work long enough with a language and figure out most its quirks, it's a breeze. It's nice that they are adding all these new features, but they are hardly what makes it or break it for me. Here is the one features that is taken for g…

Once you throw that stuff in K8s, you’re back to 10seconds.

If I throw my dinner in K8s, will I get back filet mignon?

Re: PHP 8.1.0

#87
post #50

Say what you want about PHP, but here we are decades later. I'm still using it, it still works, and it's still getting updated and improved.

Say what you will about JavaScript...

I use it constantly not because it's well-designed but because TINA (there is no alternative).

[] == ![]; // true. Go ahead. Run it in your console...

Re: PHP 8.1.0

#88

I've been using PHP since 5.x. Often had to work on older 4.x web apps. I find it interesting when I read people saying "PHP has come a long way. It's a proper language now, etc." If you work long enough with a language and figure out most its quirks, it's a breeze. It's nice that they are adding all these new features, but they are hardly what makes it or break it for me. Here is the one features that is taken for g…

With a proper type system you don’t need to run your code 50 times a minute.

With a proper type system you can't.

What a useless thing to say. The ap is talking about a tight feedback loop and you decide to make a condescending comment about type systems. Go back to twitter.

Re: PHP 8.1.0

#89

I've been using PHP since 5.x. Often had to work on older 4.x web apps. I find it interesting when I read people saying "PHP has come a long way. It's a proper language now, etc." If you work long enough with a language and figure out most its quirks, it's a breeze. It's nice that they are adding all these new features, but they are hardly what makes it or break it for me. Here is the one features that is taken for g…

When working on PHP only I didn’t care at all for the quirks or missing features. When going back and forth with other languages, PHP getting better becomes a huge quality of life improvement, the mental load we need to keep gets much lower.

PHP has always been a powerful language where the burden of making it work properly 250% relies on the dev. Stuff like enums should significantly reduce that ratio, it’s a big deal I think.

On the debugging part, I found something like ruby’s pry to be the easiest and fastest option. I wish PHP had something similar.

Re: PHP 8.1.0

#90
post #19

Who is still using PHP anno 2021?

Considering just WordPress powers something like 40% of the whole www, I'd say quite a few people!

Considering how popular Drupal is with large government applications, PHP is going to be around a long time.

PHP has become better and better over the years!

Post reply on HN