I don't think the argument that the mere existence of clients that work differently ruin the modern features somehow is really that fair (see below). The bouncer argument is kinda fair, but if you also don't like to live in a walled gardens (slack or discord), it limits the options a lot (although there are IRC servers that have integrated bouncers! Matrix is kinda like running your own bouncer again, unless you are ok with a third-party running it for you).
I can also accept that there are many more non-modern IRC clients than modern ones that work the way you would expect, so the overall expectation would be biased.
And that probably it was too little too late.
But I think you are overthinking it by a lot. If you were to use IRC, you should just use a modern "magical" IRC clients and not worry about what happens in the background (and btw it's not just "could" but "does".. there are clients that do all that already - where you can just drag and drop stuff in and it will magically do the right thing). And I am willing to bet that in other instances you already do operate that way. Unless your mail client is very broken it will send a plain text version of your email along with the html email. Do you worry there too that I am actually just looking at the plain text version of your email and not with the intended html formatting?
Or do you worry that the person you are talking to on slack might just be connected via matterircd via IRC (or directly via IRC back before slack did the bait 'n switch) and not see any of your snippets, images, etc.? Which btw. I am totally doing despite how much it butchers everything - I just cannot stand that UI (and neither can my rather old laptop).
> I don't think the argument that the mere existence of clients that work differently ruin the modern features somehow is really that fair (see below).
It totally does, though. If I write an emoji thumbsup, and the recipient only sees a tofu box, they won't know if I'm agreeing, disagreeing, or saying something else.
If I'm participating in a heterogeneous environment, I need to refrain from including any mission-critical information in a form that can't be read by all of the participants. And since writing the same information twice is usually too much work, the extended functionality winds up completely unused, or at least only gets used for low-value spam.
> Or do you worry that the person you are talking to on slack might just be connected via matterircd via IRC
Yes, I do worry about that. If I find out that one of my coworkers is using a Slack client that doesn't implement all the functionality in the reference client, and can't just talk them out of it, then I'll have to make sure not to use anything that they can't see.
I might even start doing an IRC bridge myself, in fact, since at that point there's really no actual purpose in running a chat client with a bunch of functionality that I cannot use.
A major part of Slack's value is that this is very rare. Almost everyone just uses the reference implementation.
But I think you are overthinking it by a lot. If you were to use IRC, you should just use a modern "magical" IRC clients and not worry about what happens in the background (and btw it's not just "could" but "does".. there are clients that do all that already - where you can just drag and drop stuff in and it will magically do the right thing). And I am willing to bet that in other instances you already do operate that way. Unless your mail client is very broken it will send a plain text version of your email along with the html email. Do you worry there too that I am actually just looking at the plain text version of your email and not with the intended html formatting? Or do you worry that the person you are talking to on slack might just be connected via matterircd via IRC (or directly via IRC back before slack did the bait 'n switch) and not see any of your snippets, images, etc.? Which btw. I am totally doing despite how much it butchers everything - I just cannot stand that UI (and neither can my rather old laptop).