On Tue, Jul 23, 2013 at 10:28 AM, Derric Atzrott < datzrott@alizeepathology.com> wrote:
<snip> >Since the devs implemented resource loader it has become >harder and harder to block the poorly developed bloat that has crept into >mediawiki. I used to be able to isolate the JavaScript file causing the >issues (I remember BITS geolocation being a major hog) and just block it. >Now thats not possible any longer. <snip>
Slightly off topic, but for this problem at least you could try using ?debug=true which will turn off that portion of Resource Loader.
Thank you, Derric Atzrott
That would only work for a single page, the next link I click on the debug
flag is ignored. Such a method becomes unfeasible with any serious usage.
If Source editing is going to be supported for a long time, what reason is there for not allowing users to turn off a broken piece of software? I just did a quick look at bugzilla there are 618 open bugs for VE alone. The community is demanding the ability to disable this. Ive lost count on the number of pages that it has broken. It drives editors away and prevents new users from editing. What are the real pros for VE right now? Other than a few WMF staff saying *Because I said So* I haven't seen any real progress. Just like with notifications This was poorly thought out and poorly implemented long before it should have gone live.
Ive seen this posted elsewhere, but why wasnt this tested thoroughly and rolled out slowly to ensure minimal impact and minimal site breakage. The WMF shoved VE down everyone's throat at least 6 months before it should have gone site wide. (Why? just to meet some artificial deadline that they created themselves )
What should have happened was a scaled deployment process that slowly rolled out to ensure minimal negative impact. Here is just one example of how it should have been rolled out:
1 Closed Beta on major wikis (those who know the software can test it in an actual environment that's not in a lab) 1-2 Weeks 2 Open Opt-In Beta At least 60 days 3 Step back all bugs reported 4 Enable for a small group of users who understand the wiki (AKA enable for sysops) Minimal testing 60 days 5 Listen to feedback, fix bugs and address issues. 6 Incrementally roll out to larger sub groups in 2-3 weeks intervals 7 Once a working stable product without major issues has been developed roll out to all registered users 8. Stop re-assess impact, feedback and issues associated with the project, listen to users and resolve any outstanding issues. 9 Deploy to all users once a stable, bug free product is ready.
Until the time where you are going to force people to use VE and discontinue support for the Source Editor there should be a method for disabling VE. I know I am not alone stating that I hate to be someone's guinea pig. Ill switch over to a new product when I feel it offers a better product. I would rather not have stuff shoved down my throat and told its good for you. (If its being shoved down your throat it is rarely a better product)
John