Nah I was just enjoying the irony that you and Ty were both arguing about this hypothetical Druid Job addition, vs 'no rework CNJ to be the solution to the problem', neither realizing the truth of the matter, that it's already in the game in some form.

There is definitely implementation issues with trying to make it so CNJ can be 'able to participate', and it would, agreed, be weird to have that be the only class that is able to do this 'competes with it's Job equivalents in it's role' thing. But every solution would require implementation issues. I guess the question is 'which has the right balance of 'few issues' and 'satisfies the playerbase'', and as much as it pains me, I get the feeling that SE's answer to the issue will be something along the lines of 1: do nothing.

You're right in that adding a new job would just repeat the issue, of 'I wanted to have X job, but with actual gameplay'. So I guess the solution I'd pose would be to have a new job that isn't tied to a 'fan following'. In essence, what they did for RPR, create an entirely separate, new aesthetic/job name, not tied to any previous named FF job, and make it accessible as soon as you can swap classes in game (same as how Rogue works), or if they can actually do the work required, put it as a 'starting class' (and put Rogue there too while they're at it). No need to complain about 'my favorite aesthetic got screwed by trash gameplay' when the aesthetic has no basis in FF history, right?