In 2013, @fabpot started a challenge of creating a Symfony app with only 1 file and 200 lines of code.
Today, I showcase how far we get with modern Symfony in my latest blogpost:
https://t.co/95UP0AejHh
New blog post on how we manage env variables to configure our applications in Kubernetes, to allow changing them without a redeploy:
https://t.co/r4ck0u1HZ4
https://t.co/fzAmplN0Uu
To celebrate 20 years of Symfony, I've crunched a bunch of numbers and share some memories of Symfony development since the 2.0 release in 2011.
@jeffrey_way The nice thing with syntax highlighting is that it doesn't have to be strict or validate the syntax.
The private(set) syntax probably works out of the box for most, as private is already a keyword in the property definition and (set) will just be ignored (get the plain color).
@weaverryan@symfonycon Would love to see you there next year! ❤️
I'll certainly miss you in the hallway track the next days, but it's for the better cause 💪
Agreed. The value of PR descriptions is often in things that are NOT directly inferable from the changes:
- What original problem led to this PR?
- Are there related issues / prior discussions?
- What alternatives have been tried? Does this supersede previous attempts?
- Why are certain seemingly unreasonable choices made? What are the tradeoffs?
AI that generates summary based on the changes of an isolated PR is not really helpful in a meaningful way. Good PR descriptions need not only a holistic understanding of the entire codebase, but even the contribution history of the project. That’s of course harder to do, but I think it’s a possible direction to make it actually useful.
New post on my blog:
📝 Store Code Discussions in Git using Git Notes
https://t.co/sAbnvVM7Up
We distribute code using Git, but the discussions in pull requests are just as important! I'll show how Symfony also distributes the discussions using Git.
@GromNaN@GrahamJCampbell@enunomaduro But also, PHP 8.1 is almost 3 years old and in security fixes only phase.
Any codebase that is actively developed should not be blocked by that 😅
@enunomaduro MD5 and SHA-1 are useless today.
For non-secure hashes, use the faster XXH algorithms. https://t.co/vN16aLgIHn
For security purpose, use secure algos with a seed. https://t.co/n5Yqqzg9vs
@VotrubaT@switchtrue_ As far as I'm aware, sub-splits of Laravel are in the illuminate vendor. Are you sure laravel/container is the package you want, and not illuminate/container?
https://t.co/Ttw1ldt472
@YonelCeruto And to finish the challenge (that is, without Symfony UX): you can use \Twig\Environment::createTemplate('<!doctype html>...')->render() to fully inline the template in the app.php file as well, moving everything to 1 file.
@YonelCeruto Yes, going to write a blogpost about it soon as well. Symfony has improved a lot between Fabien's old challenge and today.
Btw, in your example you can make the Kernel class anonymous and reduce it to even more lines of code :)
@Nekdev@lyrixx GH doesn't allow to specify closure reasons. It's not "we don't want this feature", but it's "there is no way to implement this feature atm (that is worth it)".
If someone has a great new idea on how to implement it, or a new PHP feature allows for this, we're happy to reopen!
@welcoMattic@VenetAxel1 You don't need to use PSR-7 yourself if you use a dependency that "is compatible with PSR-7"? Or do I miss something important here?
@_Codito_ It's even more stupid because it was a very simple string replace for some days/weeks in production, leading to all sorts of security issues with domains ending in "twitter.com": https://t.co/X4OlznNRT6