On Mon, Jun 4, 2012 at 4:48 PM, Mark Hahn <[email protected]> wrote: > > . jQuery has a history of making non-backwards-compatible changes. > > I have never been hit by one. Can you give an example? I'm not referring > to changes that relate to undocumented behavior. >
attribute selectors no longer support @, .clone( false ) was dropped, .add() now sorts in DOM order, .attr() only looks at attributes not properties, .val() behavior changed for radio/checkbox, etc. The list goes on. > I was referring to a blog entry by resig where he was bitching that he > tried to make an incompatible change and the community revolted and he had > to undo the change. I can find it for you if you wish. > You're probably referring to .attr(). The result was not backing anything out, but instead adding a shim for specific common properties (specifically boolean attributes). This shim is planned to be dropped in the future. > I have no problem with deprecating. That is the friendly way to handle > these things. Causing pain among the base is not the way keep them happy. > Yes, but you'll only be unhappy for a short while. Keeping nextTick() as it is now will cause confusion and bugs for eternity. BTW, this is the response you would actually get from the current jQuery BDFL. If you know you have a mistake and fixing that mistake isn't going to kill all of your users, then you should fix it now. Node is young, the proposed change isn't horrible to deal with, and leaving it will just result in problems continuing into the future. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
