You don't need to explain it. I know how it works. What I'm saying is based on these changes its better to stay in 1.7.10. It's not like mod developers care about which version its in. There's also the rumor that minecraft will be moving to C++ instead of Java due to the fact that mobile and Windows 10 Mc both are in C++, so that Microsoft can update easier.
What this means is modded will have start from scratch. A clean slate.
I'm not sure THAT'S true either - some mod developers only started in 1.10-ish, and I don't know enough mod developers to say as an absolute that they don't care - do you?
if so, that's awesome!
And I wouldn't call it a clean slate, but a BLANK slate. We'll be in a far worse state than that going from 1.7.10 to 1.10.2, and you surely cannot have missed the number of complaints, all the "why isn't X in Y modpack?" "What do you mean it's not ready?" "Why don't they just port it across, it's easy isn't it?" "Ugh 1.10 is so BORING/EMPTY/WEAK compared to 1.7.10/without X mod in it" or "the 1.10 version of X is so buggy, why can't they just port it, it's simple, I never had these problems in 1.7.10". You must know what I mean?
Now, I think it has a pretty respectable number and range of mods, and some very interesting ones/versions that are exclusive to 1.10+, but for some people it's still far too lacking. Imagine that ten times worse. No, a hundred times. THAT'S what you would get.
Now it may well be that this is the way it will go, in the end, and if it does I will - as I have been - advocate patience and tolerance, because it's entirely down to the inventiveness, imagination, skill and generosity of mod makers that we have been as lucky as we are. But what I've seen in this transition doesn't exactly make me hopeful about how it will go.