This makes sense. However, what kind of company culture does this set? If the company is OK with people being not passionate, what kind of signal does that give to the colleagues who want to be eager, passionate, driven?
Over the years I worked on native desktop apps, mobile apps, a Scala backend.
Now I work on a complex React app in TypeScript with a GraphQL backend in TypeScript. I can build a feature end-to-end. From domain modeling to an API to UI with animations. Optimising SQL queries.
There are people like this. Software engineers who have experience across the stack.
I don't do devops but I've met someone who can do full stack app development and devops pretty well too.
One way would be to share the article with them and explain that replies directly in a channel make it harder for you to catch up. Saying that threads make it easier and quicker for you to decide what to read.
I usually start by proposing an idea to a small group of people - e.g. my team or people at the company I think might like the idea. Only after a few people say they like the idea and start using threads, propose the idea to more people and say "look, a few of us are using threads and it works".