I recall thinking the same thing before but didn't say it as simple or concise. Nice, but idk if SE wants complexity over simplification.
Printable View
I've seen it succeed, I've seen it fail. I obviously can't say they'll do anything like it with certainty but based on their existing decisions with skill culling and job skills, it seems like an obvious avenue for them to try. It sidesteps the skill bloat, gives a means of customization and creates an easy way for jobs to differentiate themselves in group content. Ex: Two of the same tank, one can spec to MT with more defensive buffs, the other can spec to DPS with more damage buffs or dps can spec towards group utility or personal buffs.
I see potential in the system...but the devil is in the details and SE isn't known for their flawless execution of ideas sometimes.
And the question becomes: Why even bother tying it to the base class then?
At that point, you have effectively two separate jobs. The only benefit of tying them to a base class then is to reduce the leveling load for leveling all jobs because you level two for the price of one. You could just adjust XP gains and requirements instead, same effect.