Is there also a way to test the deploy works *before* I point my domain name to it? All of this is very confusing to me :(
I never really got GitHub Actions and so Forejo being based on that just really fucks with me. But then GitLab CI has become a monster of it's own now too compared to 2019 when I set it up.
I'm trying to move my website from GitLab to @Codeberg and ngl a bit overwhelmed with trying to figure out how the CI works for git-pages.
Can I use the CI or do I need to register before hand (I'm getting mixed signals) Is there a CI validation file somewhere so that I don't try to debug CI by just smashing it? Is there a cache for my PHP dependencies? How do I know all the extensions I need are in the 8.5-cli image? Yes I have a custom whacky static site generator, but it is my playground.
RE: https://phpc.social/@ramsey/117451064521285682
That is the quote :)
I personally cannot start trusting someone that mostly uses AI as they don't gain a *personal* understanding of the project.
New article on my blog about a potential use case for #PHP's 8.6 PFA feature: https://gpb.moe/blog/pfa-strict-fns.html
Would you use this? Or is this just a curiosity?
Started deploying the nuclear option on the Internals mailing list, because fucking hell some people really don't know how, or want to, read the room.
So really if WP cannot be bothered to engage with Internals, attempt to upstream features that would be useful to them and the rest of the ecosystem, and wants to support ancient versions for business reasons, why should I, a PHP core developer trying to move the language forward, engage with WordPress? I'm not going to spend my time trying to understand the ecosystem and find ways to improve it when I could do literally anything else with more cooperative parts of the ecosystem.
Spitting out that contributing upstream feels like it is not worth your effort, even if it would help everyone, because you can't use it for years due to supporting ancient versions is one of the reasons why WP is seen as holding PHP back.
I've only ever seen WP developers use Rector to *downgrade* their PHP code as they want to write modern code. Nobody asked you to maintain PHP 5.2 compat in 2019 (for WP 5.1). For context this means no namespaces, as this is a PHP 5.3 feature.
It's been a solid few hours and I think the thing *I* find the most frustrating is the self inflicted problems and complaining about the consequences, which is kinda highlighted by this quote hidden in the sea of why does the rest of the community view us a certain way:
> [...] even when it makes something better for WordPress, it may still take ten years for WordPress to be able to take advantage of them due to the long-tail support for older PHP versions.
> WordPress doesn’t need much from the language and has always been conservative in adopting language features. Server performance and security are what pull WordPress in; language features are pushed harder by frameworks like Laravel.
I'd love to hear the opinion of some of the other PHP CMS and eShop platforms as this seems like a whack justification. Because if you didn't need much from the language, upgrading *should* be easy and straightforward. As the surface you rely on is minimal.
And this is not new, as from what I know WP refused to participate in the Go PHP 5 project (https://gophp5.org/).
This was before my time, so maybe I am wrong. But when as a project you have a pattern of not pushing the ecosystem *forward* you will, quite naturally, be seen as holding it backwards.
> Part of this is due to WordPress being seen as dragging PHP backwards because of its backwards compatibility commitments.
Maybe because WP quite literally prioritises keeping support for *ancient* PHP version rather than newer ones? WP 6.2 released in 2023 *still* supported PHP 5.6, 5 years after it was EOL (PHP 8.2 was the latest stable at the time). [1]
I don't expect day 1 compat with a new version, but there is a *reason* why the community feels this way.
[1]: https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/
> Upstreaming spec-compliant web standards into PHP: HTML parsing, URL parsing, HTTP header parsing, Query arg parsing, MIME content-type inference. This is an area WordPress could help improve or sponsor work on, which would benefit WordPress and PHP at large.
Gee yeah that would have been useful to do *years* ago, and not realise this now *after* a new HTML5 compliant parser for DOM was introduced in 8.4 and URI parsing in 8.5/8.6 has been added with query parsing already being worked on.
> Opportunities for overlap with PHP Core
IDK have Automattic pay for someone to monitor the list and RFCs? I truly don't understand how with over a thousand employees this *still* is not the case.
Tell me you don't understand PHP without telling me directly:
> WordPress requires only a small number of PHP extensions (currently just json and mysql). Per the data from sites phoning home, PCRE is present on 100% of WordPress sites and could be made required.
PCRE is *always* present in PHP since 5.3...
What the F is the community meant to do for WP if WP doesn't even understand the technology they use.
Dear #DuckDuckFedi
What is a good *easy* music tagging software to tag album and artists for various different formats (mainly FLAC and Oggvorbis) so that my GF running Arch can fix her music files?
Flying to Toulouse from Heathrow this morning I had some unexpected luck!
So people want to see some live coding.
I'm going to _try_ to do a stream tomorrow around 1400 BST, implementing the proposal likely to pass from the #PHP 8.6 mass deprecation RFC.
Will be at https://phpc.tv/c/rant_time/videos (hopefully)
Not sure if following @girgias@phpc.tv or the channel will give you notifications directly on Fedi :thinking:
Well this went *somewhat* okay! Audio issues aside that I'll need to improve/fix.
For next time what should I do?
Hopefully this works: https://phpc.tv/w/iqc6gh5hdezm9Ltq5nY1PD
PeerTube doesn't seem to make it easier, or I just don't get the interface.
https://phpc.social/@Girgias/117026297203619976
You gotta love that the single train journey from Munich to Budapest with a seat reservation getting cancelled by ÖBB turning into 3 journeys with no reservation is infuriating.
Especially as there is quite a lack of clear communication and no mention whatsoever of possible compensation...