Two major flaws with that approach.
First, we're talking about a core mechanic to the class system, which is the Armory. The reasons for keeping these systems have already been addressed, but removing them essentially would involve some pretty major work and re-coding. After already doing such a significant investment, especially when we're talking about setting a framework for future developments. The longer we go the far, far less likely we'll see it so dramatically changed.
Second - this isn't a new conversation. The argument against the class system was introduced before Jobs were introduced, and then was asked to be removed as soon as Jobs became mentioned. Put frankly, it's been over a year already and the answer has been rock solid. Continuing the conversation will not make them cave, especially as research has indicated that the outspoken opinion is contary to the open one.
This is ignoring the fact that we're doing this based off of dated knowledge.
Or the fact that honestly, the "class" part of the class system can mostly be ignored by players who don't like classes. (Simply turn on your Job mod and never go back to Class modes, equip a macro so it's done for you.) So the request itself is talking about removing content against a base that also enjoys it.
All of this has been said, not just by those who oppose the OP's suggestions, but by development as well. I could write an FAQ for people to copy and paste as a response to every possible angle you could take this argument, and likely never use my own words. It's been discussed that much already. We don't need to keep arguing in circles over something the Devs have already addressed. It's insanity.