4 ms·

Been using it so far using a PPA with my own unreleased Python dialect that compiles to PHP. Gonna be a solid release. Amazing to see so much evolution for PHP

• datalopers 4y ago
  Fibers were released in 8.1 but are there improvements in 8.2? I'm curious to see how useful it is until a lot of core libraries (curl, redis, mysqlnd, etc) can be called non-blocking and/or trigger a fiber yield during a block? My understanding is swoole does a whole lot of work to enable hooking into those to allow coroutines, which won't implicitly exist with fibers?
  • geenat 4y ago
    IMO, unless I am mistaken, using a continually running PHP process like Swoole removes advantages you get with vanilla PHP: fully isolated requests, file based routing, etc. This is why fibers are so big. It'll bring performance without the downsides.
• vedranm 4y ago
  Coroutines have been available via many packages for a while; (Open)Swoole and Amp come to mind, but there are probably others. Laravel has supported using (Open)Swoole via Octane for over a year. Why would having coroutines as fibers in the core be a gamechanger?
  • geenat 4y ago
    See: https://news.ycombinator.com/item?id=32726419 https://news.ycombinator.com/item?id=32726419 Performance without downsides.
  • capableweb 4y ago
    > Why would having coroutines as fibers in the core be a gamechanger? Plenty of technical reasons but for me, the biggest is unity among libraries/technologies. There been versions of coroutines/fibers around PHP for many years, first time I heard about it was a PHP fork that implemented fibers, don't recall the name but must have been something like 10 years ago... But the problem has always been that you cannot rely on the community having things like that available. Having it in the core language, means that more libraries can depend on it, and users are therefore incentives to learn more about it, as they can rely on it sticking around. Overall, I'm happy it's coming into the core language.
    • rob-olmos 4y ago
      > first time I heard about it was a PHP fork that implemented fibers, don't recall the name Probably thinking of HHVM/Hack: https://docs.hhvm.com/hack/asynchronous-operations/introduction https://docs.hhvm.com/hack/asynchronous-operations/introduct...
    • vedranm 4y ago
      > Having it in the core language, means that more libraries can depend on it, and users are therefore incentives to learn more about it, as they can rely on it sticking around. Symfony 6.1 and the upcoming Laravel 10 require PHP 8.1+, but I don't see them using fibers yet. We'll have to wait and see.
• nerdponx 4y ago
  What's the benefit of compiling a Python-like language to PHP instead of just using PHP?
  • lowercased 4y ago
    Existing familiarity with a python-like language? Lack of motivation to learn the intricacies of PHP? (valid reasons and I'm not trying to sound sarcastic here).
  • ksec 4y ago
    Avoiding PHP syntax alone is a big plus to me.
• progre 4y ago
  It's the $varname syntax right? I get angry about it too.
  • geenat 4y ago
    ; is optional { and } is optional $ is optional new is optional attribute access -> is now . associative array (dict / map) => is now :
  • parasti 4y ago
    I think the $ syntax is the best decision they ever made. It's probably why they can keep modernizing the language so successfully.