> but it also doesn't do much harm in practice

I digress on that.

I have no fucking[0] idea if Firefox 99 is just a minor upgrade over Firefox 98 or it would completely change the UI and my UX with it. With X.YY to X+1.00 I could, at least, be warned what something crucial could change. Nowadays I'm the hostage of "We think you need to do things THAT way" of whatever fever at Mozilla corp at the moment.[1]

[0] I mean it.

[1] There was something about themes or colours or whatever in the last ten updates. Did you used it more for than a day?

(Totally agree!)

You mean "disagree" here though - "digress" means that you step away from the topic for a moment.

> step away from the topic for a moment

From the topic of the article in this case.

Just the fact that both Firefox and Chrome are version 100 as we speak is pretty suspect by itself, not that it really matters why they did it

So trying to shift development processes more toward continuous delivery (within reason, given desktop software) is meaningless, then? Come on.

Sure, do that. But by chance they are both on 100?

They each release on a regular schedule. I don’t think that they have the same schedule. You can see each of them incrementing with each release. They have been doing this for several years now. It really is just chance they they are at 100 in roughly the same time.