Richard brown did post his promised blog on why not to use Leap and go Tumbleweed (well, really, MicroOS) only...
https://rootco.de/2020-02-10-regular...ses-are-wrong/
For me, the great strength of Tumbleweed, as a "general purpose" distro, is also it's greatest weakness; constantly rebuilding packages. Watching zypper dup download and then individually update 1000+ packages on a weekly basis or more is a bit much to me, even for a single desktop. On a general purpose sprawling server that feels like a nightmare just waiting to happen.
On the other hand, I do fully agree that rolling for Micro OS and single function containers, where a whole pre-made system image snapshot is provided that is a product delivery or an update, makes a lot of sense. I don't have to watch 1000+ packages try to individually update, running their scripts, etc, and hope nothing goes wrong. I just re-image each application service, once, when I want to update. Even the great anxiety of rolling distros, of what happens if I don't update for several weeks or months, is gone, as it is always installed as a clean snapshot image rather than trying to rebuild itself from individual packages all running scripts, and any one of which that may assume an update you may have missed had already been installed.
If Richard Brown is proposing things like Micro OS with rolling single snapshot updates (and ideally an immutable rootfs) should entirely replace conventional servers, I could fully embrace that. If he is proposing that rolling distros should be the only form of all linux distros for all uses, which he also advocates, I feel he is dead wrong there. For example, for development work and generic desktops, having used both now, if I had to choose, I would pick leap over tumbleweed.