Why do the devs hate MCH so much?

[ForteNightshade]

Uhm, no. It has only become an issue this tier because the massive hitbox the raid boss have, something that are widely acknowledge both by community and developers. And they already said moving forward this will be recetify. There are a reason the community have always come up with "melee uptime" strat that usually carry more risk to the party. Even this tier, certain mechanic still have optional uptime strat (Ruby 5 in P5S, Exchange 1,2, 4 in P6S), but they're often deemed too risky to be adapted in PF.

I'm playing both DRG and a BRD, if you can convince me mobility simply doesn't matter, than you can also try to sell me a bridge.

You do realize the role bonus was introduced because the dev team literally couldn't balance the Phys Range, yes? In fact, in 5.0, they were so weak it was actually better to drop them entirely and just suffer the 1% loss. They had to panic buff them prior to TEA's release due to have hilariously undertuned all three jobs were. Bard, in particular, has been an absolute mess since Dancer's introduction. And I really don't know what else can be said about the disastrous state of Machinist over the last four years. All because they've been desperately trying to balance a role within arbitrary limitation. Whether it be mobility, ease of rotation or utility. It had repeatedly led to near constant imbalances.

And we've already seen their "rectification" when 6.25 dropped. They slapped on baby buffs after Dancer once again completely dwarfed its counterparts. Now Bard exists while Machinist continues to rot for another patch as they've already said 6.3 will only have the Paladin rework. In other words, they did absolutely nothing about the mobility tax and are hoping people forget about it.