That's what's been happening with HTTP. Now browsers are bloated and take a lot of system resources to run.
IRC is unable to do this because it requires a constant active connection which is something that was fine in the desktop era but is not usable on battery powered devices.
Conversations.im works this way and has minimal battery impact. iOS doesn't allow this, because it's easy to get wrong.
Ah, I didn't know that's what push notifications were. Sounds like a regular old pull aka refresh but I have no idea about web stuff.
> IRC is unable to do this because it requires a constant active connection which is something that was fine in the desktop era but is not usable on battery powered devices.
I think at the scale which devices are already waking up to check things, it's unlikely to be a problem for most. Phones don't actually sleep for hours (or probably even minutes.
That said, IRC's heavyweight connection does seem clunky, if your connection drops momentarily it's unlikely you wanted to lose track of conversations you were currently participating in. Although that can be solved with logs / archives pulling what you missed, it seems better solved at a core level (maybe it is, I haven't looked at IRC for a decade or more).