Théo Fidry

For those encountering issues with Hautelook AliceBundle, you can find more information here: github.com/nelmio/alice/i…

@GromNaN Def. agree, although let's be honest, multi-ternary (or multi-expression statements) on one line are always hard to read

When chained, the ternary operator syntax is hard to read. I prefer a using match(true) #PHP

🙌 Remembering Ryan Weaver: Teacher, Core Team Member, Friend ➡️ symfony.com/blog/rememberi…

@VotrubaT @kubawerlos Thanks a lot Tomas, it is very appreciated 🙇‍♂️

I've decided to add two more amazing devs to the list! 👇 @kubawerlos @tfidry Donation is on the way 🫡 thank you for your work

@mitsuhiko What is the root cause? (not very familiar with Rust, pardon my ignorance)

This is from the 2024 Rust survey. The first three items all have the same root cause. I wish there was some reason to be optimistic that this could improve, but I don’t really see it.

@Shyim97 @dunglas @Vonage I find it really interesting, because despite all of those valid points, even as I learn other languages, I'd still pick PHP over TypeScript/Go/Python/Kotlin 🙃

@dunglas @Vonage I would not choose PHP for any new project tbh, missing async functionality in widespread packages like Symfony or Doctrine the toolchain is annoying there are not one php many combinations due to installed extensions and everything scoped system-wide. composer is not bundled

PHP is legacy, in 2024 (by @Vonage). developer.vonage.com/en/blog/php-is…

@pronskiy @phpstorm _proceeds to delete all of my codebases_

Okay, here is an impromptu challenge: share how often you delete lines according to Help->My Productivity in @phpstorm. Whoever deletes the most wins a PhpStorm elephant 🐘

@pronskiy @phpstorm Holy

@tfidry @phpstorm Help -> My Productivity

Apparently I delete lines and use multiple cursors in @phpstorm far more often than I use code completion 😁

@matthieunapoli I don't know the project but I do take you for a reasonable and experience person that can make a sensible judgement about this 😄 I think DDD is just a tool to help estrablish and detect boundaries/constraints. Sometimes the result is just that you're highly dependent on infra

@tfidry No: in that project it must be thrown out the window

It's been interesting to work on a very high-scale project: the usual DDD approach (writing infrastructure-agnostic code) must be thrown out the window. Infrastructure details are interwoven with domain logic because of the high traffic/volume.

@matthieunapoli But I like to see it as a much more contrived example, which doesn't even need to be about DDD: Hard to explain on Twitter though: 3v4l.org/fh93m

@matthieunapoli I mean the first post was pretty much: you need perf => throw DDD out of the window ;)

@alex_s_ @_Codito_ @martinbean But surely creating entities is cheap? I would avoid any DB/FS call in there as much as possible, but I don't see how creating objects in the data provider would be a problem

@_Codito_ @martinbean Keeping complexitiy out of data providers is good. Because all data providers are called even when you filter only by a specific test case. Something I did wrong in the past creating entities inside of them, instead better return only scalar values in them: Docs:

Since PHPUnit adopted attributes, I’ve much preferred specifying test data above test cases using the TestWith attribute, rather than referencing a data provider with its implementation elsewhere in the class. An example of before and after 🔽

Doubt you would not be aware of it but better safe than sorry @philsturgeon : youtube.com/watch?v=R0d7Ho…

@jderusse @alex_s_ @goetas_asmir @_Codito_ it's very light though, so in the end I always end up using it. It always makes me miss a pipe operator though

@alex_s_ @goetas_asmir @_Codito_ and breaks ~all the benefits of using iterrables 🙁 I would have loved that array_map/filter/... take an iterrables instead of array. I once used github.com/nikic/iter on a pet project. It does the job but maybe overkill in many cases.

I would say: avoid using arrays (especially in a public API), but when you really need to use them, describe them properly 👌.

@nicolasgrekas Congrats! It's a nice and big change!

The vote passed! 🥂🥳 #PHP 8.4 will provide lazy objects natively!

A big ask from a big community gofund.me/798e5c3e #php

@vanamerongen Reminds me of the useless auto-generated php/java doc "This is the constructor" that the IDE was adding all the time. Yeah no shit

Really irks me when people request I document things with comments that are already perfectly conveyed by naming. Like I'm literally just commenting what it already says it is

@marcelpociot In my experience, if you do pic sync, you should at least include a serialization step

How do you work with queues in Laravel locally? Do you just use the "sync" queue driver, or redis/database and then start the worker manually?

@vanamerongen @mootoday IMO git hooks are like IDEs: let people do what they want, enforce rules via the CI And if one forces git hooks, I'll alias git commit to add `--no-verify`: let me hook free

@mootoday --no-verify or just rename the hook file, lol Why wouldn't you want them in your CI in the first place? They take like half a second

@MabarDev @janedbal @OndrejMirtes But all of that introduces dependencies and slows it down 🙃 I really like the idea of the tool, but I also feel you'll always hit a limit with a token base approach (although it is much faster)

@janedbal @OndrejMirtes - allow indirect dependencies from specific packages. I have a CMS defining a ton of dependencies and I consider dependency versions to be part of the API. It allows me to require one package in an extending module instead of ~40.

🚀Boost your CI pipeline with github.com/shipmonk-rnd/c… • Uncovers unused, shadow and misplaced #composer deps • Scans 15 000 files in just 3s!⚡ • Fine-grained ignores • Supports #php 7.2 - 8.3 • Zero composer dependencies • No config needed for first try Try it today!💪