News for hackers. Stuff that matters.

A comment on Tragedy of the WebKit Commons.

Re:Tragedy of the WebKit Commons by kevincennis on Wednesday February 13, 2013 @09:50PM (#5217372)
It's really interesting to get the opinion of a jQuery core contributor on this whole thing. I can't imagine very many people are in a better position to comment on the state of current WebKit bugs than the folks writing the most popular DOM/AJAX library on the web.
[ Parent | on HN ]
Re:Tragedy of the WebKit Commons by MatthewPhillips on Wednesday February 13, 2013 @10:45PM (#5217566)
He had me until he put bloated (as a description of jQuery) in quotes.
[ Parent | on HN ]
Re:Tragedy of the WebKit Commons by scott_karana on Thursday February 14, 2013 @07:26AM (#5219110)
Admittedly, he was refering to the 2.0 line, the goal of which was to drastically lower the size of the codebase by cutting out support for non-current browsers.
[ Parent | on HN ]
Re:Tragedy of the WebKit Commons by MatthewPhillips on Thursday February 14, 2013 @08:17AM (#5219269)
Feature bloat is still bloat. jQuery is a DOM library, an XHR library, an animations library, a functional library, a promises library... as far as I know 2.0 doesn't do anything about that issue.
[ Parent | on HN ]
Re:Tragedy of the WebKit Commons by dmethvin on Thursday February 14, 2013 @09:33AM (#5219569)
In either 1.9 or 2.0 you have the option to exclude XHR or animations as well as several other functional modules. More feature-lopping capability will be coming soon.
[ Parent | on HN ]