Er, no. That's like saying Linux is only CLI. It's outdated misinformation. There are loads of web clients, and you wouldn't believe what kinds of tech illiterate people I've seen on some networks.
It's funny that your parent is downvoted below zero when he's absolutely right. I don't use IRC very much, but the last time I did, I wanted to use the name I'd registered with previously. Unfortunately, Pidgin kept telling me my name was already in use or some crap. It was quite difficult at the time, not being an initiate in the appropriate vocabulary, to figure out the search terms to use to discover that I needed to "ghost" the user or some ridiculous unintuitive incantation. I may have got the details wrong, but that only confirms my point. IRC is too hard for non-techies. I'm a programmer by profession, and if it gives me the slightest hassle, it's too hard for other people.
Maybe a nice client could make this pain go away, but I doubt it. All the ones I've tried have suffered from the same learning curve problem and the same in-grained assumptions that come from regular use of IRC. Even if one were easy and elegant, I'm not sure that could overcome the negative network effects of so many clients, billed as IRC, doing it badly. I'm not going to analyze it in detail right now, but there's myriad subtracting reinforcements from a community that mostly uses user-unfriendly clients and protocols. You can't just make one good client and get a tipping point. In fact, desktop linux does look like a good analogy here.
Moreover, it would be disingenuous to claim that IRC being techie-unfriendly is "outdated" when the majority of clients and tech how-tos pointing to clients are the same as they ever were. I would guess that the majority of IRC use is still done on unfriendly clients, e.g., Pidgin. One or two low share clients existing don't speak for IRC.
Now, I'm not saying XMPP or this client is an answer. But, yes, IRC is and always will be unpopular with the non-tech population.
"Based on the _libpurple_ protocol library, Adium can connect you to any number of messaging accounts on any combination of supported messaging services (see further down for the list) and then chat with other people using those services." (Emphasis mine)
"Libpurple is the library which provides network-level connectivity for most services in Adium. Like Adium itself, it is licensed under the GPL. In addition to Adium, libpurple is the core of the Linux and Windows IM clients Pidgin and Finch. (...)
Libpurple was previously named Libgaim. "
So yeah, Pidgin is an option, because neither Adium nor Pidgin speak IRC, libpurple does. The support should be ~the same~, of course depending on the version of the library used.
I wanted to switch to Pidgin a while back because it had support for the kind of encryption I wanted (public key) and Adium didn't, but I ended up not doing it and I thought the reason was because Pidgin doesn't do IRC.
"Pidgin is compatible with the following chat networks out of the box: AIM, ICQ, Google Talk, Jabber/XMPP, MSN Messenger, Yahoo!, Bonjour, Gadu-Gadu, IRC, Novell GroupWise Messenger, QQ, Lotus Sametime, SILC, SIMPLE, MySpaceIM, and Zephyr."[2]
Yep: Pidgen has supported IRC so long that back when I was still using it, and the project hadn't yet been renamed from Gaim, it already supported it; it had a few stupidities, and didn't support userhost-masks for buddy bindings (something that simply "makes sense" if you use IRC enough), but it definitely worked and still does (I have friends who use it all the time for IRC, and one who even contributes patches to it).
