Because its always been a bad idea, it gives hell for anyone who does mod development trrying to support their users, and everything should be possible through LUA scripting exclusively.
Everything SHOULD be possible through LUA, but it is not.
Unless you can show me a way to STOP WoW.exe from loading PlayerFrame.xml/lua, TargetFrame.xml/lua, RaidFrame.xml/lua, PartyFrame.xml/lua.
It does not give hell to anyone making mods to support their users, unless their users are of such a nature as they would have trouble doing most things on the computer, in which case I think the Blizzard Default UI is the best for them.
Perhaps offering the addon as a password protected file, requiring the user to type "CONFIRM" to even extract it, would be enough to discourage the masses from using it.
Of course, regardless, people will download it, then blizzard will patch, and they will complain on the Blizzard Tech Forums that nothing is working, and the culprit will be an addon the user did not update. Thus a workaround would be for a user to connect ' to the tech forums trough an application they launch from the wow folder that backups their settings, launches the game, ask if everything is ok, and then tell them what has happened. - That would of course lead to complains that "BLIZZARD RUINED MY UI (Which was already broken, since I ran the utility, but lets not mention that, since its blizzards fault)... )
How is destoying a frame in wow easier through FrameXML than in LUA. If you want to destroy a frame.. unregister its events and kill it..
Most efficient, not easier.
When WoW Launches, it reads the .mpq files as well as the Interface folder.
If it finds something in the Interface/FrameXML folder, this will REPLACE the files from the patch.mpq/Interfaces/FrameXML folder.
The result is that - only ONE version of the file is loaded - MINE.
And my file is 20bytes, whereas the blizzard one, in addition to containing a LOT of functions, onupdates and whatnot, is around 15KB per xml/lua replaced.
Every other method of destroying frames and functions is inferior to a frameXML replacement.
Its not a ban.. and the reasons are completely sane and reasonable. FrameXML may work for you to do the 0.1% of things that you need to do.. but they're a nightmare overall.. He announced this TWO patches ago, and asked over and over again for functionality that he'd need to add to the LUA environment to compensate for the loss of FrameXML overrides.
We've gotten so many presents since then.. its insane. 1.10 is a huge step.
He may have asked, but as I am a European player I have NO ACCESS to the US Forums.
And How are they are nightmare, except for when USERS dont stick with the programme, which they do not do anyway so regardless they WILL get support incidents because of USERS. If they wanted to stop USERS from reporting stupid mistakes, they would have to disallow ANY modification of the game UI. FrameXML is just the start I suspect, and eventually there will be no addons or only Blizzard Sanctioned ones.
So to repeat myself: THOSE BASTARDS.
Because they ruin functionality that I want, Need, Use, Can Cope With.