On Sat, Apr 8, 2023, 6:04 PM Ilija Tovilo wrote:
>
> Sadly, there's a conflict of interest here. There are people who want
> to keep running their existing websites without having to make any
> changes, and there are people who are using PHP daily and would like
> to see the language evolve. We w
On Sun, Apr 9, 2023, 7:10 PM Kamil Tekiela wrote:
>
> I'd rather say that the roadblocks people are facing in upgrading legacy
> projects are not specific to PHP 8, but rather a technical debt acquired
> over the past 10-15 years. Even if nothing would change in PHP 8, people
> would still compla
On Sun, Apr 9, 2023 at 7:10 PM Kamil Tekiela wrote:
> > But the cost is catastrophic. If you have a legacy codebase hanging over
> your head you probably know how hard it is to upgrade it.
>
> I wonder about this every time I hear this claim. What exactly changed in
> PHP 8.0 that made the upgrad
> But what's the point of starting a greenfield project in PHP while
Typescript is right there?
If that is true then we have pushed PHP to its death. PHP is dead and we
can move on to other projects. But that's obviously not true. I could claim
the complete opposite: why start a project in Typesc
On Sat, Apr 8, 2023, 5:47 PM Dan Liebner wrote:
> I agree with the OP's sentiment here. If I was starting a codebase from
> scratch today, I'd probably go with Node. I find that writing modern
> JavaScript is way easier than writing PHP these days, and the breaking
> changes in newer PHP versions
On Saturday 08 April 2023 22:17:14 (+02:00), Niels Dossche wrote:
> However, I think it might be worth adding an optimization for the most
common $x = array_merge($x, ...) case.
If so, then syntax wise I'd throw that suggestion in the ring:
$x[] = ... $y ;
This would allow to adopt exi
