Sergey Rabochiy

Hi there! As was mentioned, there are many queue consuming strategies: priorities, grouped priorities, weights, counters, etc. It's hardly possible to implement all of them at the same time. And...

@d-ph : > ... Perhaps [the following code region](https://github.com/symfony/symfony/blob/7edbdf8b11e9bcd976c42085d94cc8778abb6de5/src/Symfony/Component/Messenger/Worker.php#L95-L119) could be "extracted" ... Yes! It's the main idea. I've wrote [some code](https://github.com/upyx/symfony/commit/5ff924b5cc0f31645c24869a578ce85397cd85ab) to explain the concept deepper. I haven't run...

@d-ph you are in the right way. And yes, using aggregation here is slightly overkill :slightly_frowning_face: But the reason for the high complexity is overcomplicated Middawares and the Worker with...

Nice to meet you, @Guikingone :wave: I've mentioned `SchedulerBundle` because it's an awesome tool for cron like schedules, and it's a good for requests&tasks based applications (which are the most...

Nevertheless, there is a **nuance**... Hm... there are few ones :grin: Why is some Schedule/Cron/Jobs/Tasks/Etc bundle is needed when the crond/cronspec/CronJob/cronetc is already exists? Why do not configure a crontab/CloudSpec/Helm/Etc...

> I have a different opinion here So let's discuss it :) > Eg one can process N messages in parallel and ack/nack as needed. This is a desired feature...

Composer prior 2.3 uses `symfony/console` 3.4. The `isTtySupported()` method is really simple. Why do not copy&paste it to the devtool? It would be fast fix.

It's an option that I've shared. And yes, it has the same issues as the `PsrLogMessageProcessor`. I don't like it too. But loosing 60% of perfomance by logging I hate...

> How about this alternative Two creations of objects are twice as expensive. It's not good in the fight for performance.

It is not a good idea. It will break some implementations at least. Cache adapters can use any characters that are supported by their backends. If some backend does not...