We're not saying that the mod authors don't have real lives. In fact, look and you'll see I've said the exact opposite quite a few times. What we are saying is that it is unfair to the other mod developers to be kept waiting on a mod in a pack to be updated if the rest of the mods are ready.
There is no obligation? You're right. And FTB isn't obligated to keep the mod in their pack either. It works both ways. Remember that. If you want your mod in FTB, then you need to update and support it. If you don't want to update and support it, then it's the FTB teams right to remove it. Plain and simple.
Sorry, TL;DR the entire thread. I just wanted to post my opinion about the topic. Too many whiners. ~_~
Coming from the mindset of a dev (because I'm a dev myself), do you think it matters to me if a
mod pack takes a while to update, just because other mods are not ready?
If I were building a mod that's an extension of IC2 or BC, it matters. Because my code depends on them.
But for most of the mods, you can play with them as is. You don't need a mod pack to play with the mods.
Mod packs are just a convenient way to play with them without going thru the hassle, especially if you're not technical enough to mess with the Minecraft jars.
Also, I think you got the whole concept of the FTB modpack wrong. You are right about the FTB team's prerogative to remove a mod if it's not updated. But mod devs don't ask the FTB team to include their mods into the various mod packs. It's the reverse: you ask permission from the mod dev to have their mod included into FTB. That concept only works if you are trying to sell a product.
In the end, no one's stopping people from installing the mod directly from the source, or from playing with an outdated mod.
Ok, I've said my piece. My chest feels lighter now.
I leave you pips with this message:
**Drinks Invisibility Potion**