Even trying L4S is rather problematic still these days. All the support for it - from the AQMs to the transports - live out of tree in an increasing ancient 5.15 release. Where cake has been shipping for nearly 10 years in some form or another. I would like that group to get on the stick on submitting it upstream, because there are some code quality problems there that they should fix (notably GRO issues), much less the algorithmic issues that I have also pointed out!
My biggest gripe about that project is that everyone focuses on the ECN change, and nobody looks at the effects on normal everyday traffic, where fq_codel or cake utterly smoke the dual-pi AQM. There actually is L4S support in fq_codel now, but they are not testing it. :(
fair 'nuf. I'd love to hear your opinion on it - take up my point or the opposite - whenever you have the time. I would say "no offense" but I think I've offended basically everyone on earth now in this thread.
I'm Australian and have the direct counter experience. Most of the business I've worked for consider Slack as ephermal.
Email is for significant communications.
Outside of work, I'm using daily for things like booking bands, talking to strata, etc.
While email in a lot of large companies might tend to be becoming a one-way distribution system; it is still vibrant and heavily used in smaller enterprises.
GitHub repo says it was archived 2 years ago: https://github.com/Netflix/titus