On Sun, 4 May 2025 at 14:57, Jochen Schultz <jochenschu...@gmx.de> wrote:
> > > Am 04.05.25, 13:07 schrieb Arvids Godjuks <arvids.godj...@gmail.com>: >> >> >> >> On Sun, 4 May 2025 at 10:36, Michael Morris <tendo...@gmail.com> wrote: >> >>> It's been 9 months. Been researching, working on other projects, mulling >>> over >>> points raised the last time I brought this up. And at the moment I don't >>> think >>> PHP 8.5 is in its final weeks so this isn't a distraction for that. The >>> previous discussion got seriously, seriously derailed and I got lost >>> even though >>> I started it. I'm not going to ask anyone to dig into the archives, >>> let's just >>> start afresh. >>> >>> *snip* >>> >> >> I've started reading, saw Wordpress... almost stopped right there, but >> decided *okay, this is too rash of me, read further*.... >> >> "My disappointment is immeasurable and my day is ruined".gif >> It ended exactly how my first judging brain wave thought it would go - >> this whole thing is about fixing WordPress by changing the language. Plain >> and simple. >> >> No. >> -- >> >> >> *snip* >> >> I don't like wordpress either. It sure is the reason why PHP became a >> running gag in memes. >> >> But it exists. And if it goes away PHP might too. >> >> Yes, we hate it, it's a mess. But can we ignore it? >> >> I think it deserves a fair discussion. >> >> There might even be a "simple" solution to it. Maybe a version number >> that is auto-added to the namespace in composer? >> >> Maybe the wordpress community could fork composer and do it? >> Like what are we talking about? 10-20 lines of code? >> >> Best >> Jochen >> >> >> Yes, we should ignore it when working on language design and trying to improve it. For whatever reason, they made a deliberate commercial decision not to do anything about it, and this is not even touching on events of recent times :) Two - I already have to deal with JavaScript at times and all it's ecosystem. I do not want another JavaScript in my PHP, thank you. For me, any concept for modules, packages, etc, etc that ignores autoloading is dead on arrival. Ideally it should be transparent to any consuming code and be done on the defining side, erroring out when attempting to load/access something internal to a namespaca/package/module. I'm also not a fan of ability to mix multiple package versions in one code base. -- Arvīds Godjuks +371 26 851 664 arvids.godj...@gmail.com Telegram: @psihius https://t.me/psihius
