[wp-trac] [WordPress Trac] #10021: Unresponsive script errors on widgets screen

[WordPress Trac]

#10021: Unresponsive script errors on widgets screen
-------------------------------------+--------------------------------------
 Reporter:  Denis-de-Bernardy        |        Owner:  azaozz  
     Type:  defect (bug)             |       Status:  reopened
 Priority:  normal                   |    Milestone:  2.9     
Component:  JavaScript               |      Version:  2.8     
 Severity:  normal                   |   Resolution:          
 Keywords:  has-patch needs-testing  |  
-------------------------------------+--------------------------------------

Comment(by filosofo):

 Replying to [comment:29 azaozz]:
 > In principle this sounds good however in practice it would be quite hard
 to convince plugin and theme authors to learn yet another API. It's hard
 enough to make them stop bundling jQuery and use the one included in core.

 The theme and plugin authors can continue to use jQuery if they want, as
 I'm sure we'd continue bundling it as we do Prototype, for example. But
 it's not like learning the jQuery API is all that helpful anyways, as it
 has changed significantly between versions, and we don't have any reason
 to think the future will be different.

 The advantages of a WordPress-built JavaScript API is that it could be
 truly stable, mainly by focusing on a few things that always need to be
 done in the WP admin: drag-and-drop, XHR, etc.

 > If we switch to our own JS API at least one JS library will still be
 loaded on every page by a plugin or theme anyways.

 There's not much we can do to avoid badly-written plugins; they're always
 going to exist.  But the properly-written ones should be loading their
 libraries only on their own pages, with a few exceptions.

 > Also jQuery is getting better, 1.3.3 seems to be coming out soon and has
 some nice speed improvements.

 I used to hold out hope for future improvements, too, but jQuery has had
 plenty of opportunities to address well-known problems and to take
 advantage of lots of constructive criticism.  I see selector speed reports
 and the like, but they don't mean much when I can turn on Firebug in
 actual applications and profile, for example, a simple drag-and-drop with
 tens of thousands of function calls.  Or I go open a page on Slashdot and
 my CPU usage spikes for few seconds while jQuery churns.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10021#comment:30>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software