Visual Studio Magazine: "Microsoft is working in a number of directions, including databinding, the script loader and contributing to development of templating functionality as part of the jQuery core."
Oh, no Microsoft! Please, please don't ruin jQuery! Don't make it as insanely overcomplicated as your own AJAX.NET. Don't mix together JavaScript client code with server-side "loaders". Don't you understand that RESTless WEB client is not the same as .NET server or Win desktop?!
Thursday, March 18, 2010
More Details on Microsoft's plans to ruin jQuery
Comments (13)

Sort by: Date Rating Last Activity
Loading comments...
Comments by IntenseDebate
Posting anonymously.
More Details on Microsoft's plans to ruin jQuery
2010-03-18T16:57:00-04:00
Владимир
ajax|JavaScript|jquery|microsoft|ruin|
Lelando · 784 weeks ago
Nearly every response I've read misses one very important thing: MSFT will NOT be directly contributing to or coding for the jQuery project. They will be INdirectly contributing the same way everybody else does: by writing proposals that the jQuery core team can take or leave as they see fit.
So, stop freakin' out as though MSFT is gonna ruin jQuery. If jquery gets ruined by any of this, it's because the core team took bad advice, and NOT because MSFT changed something. Geez, people, what a great way to take your hatred and just jump to conclusions without knowing the whole story. Yes, MSFT has made some bad choices in the past, but they have also made some good ones. Just like any other business, they're run by human beings, and just like you or me, those human beings are bound to get some things right and other things wrong. So chill out, and wait to jump on they hyper-critical bandwagon till you know the whole story. Seriously.
Vladimir Chernya · 783 weeks ago
Lelando · 784 weeks ago
Lelando · 784 weeks ago
"We are contributing to the open-source jQuery project in the exact same way that any other company or individual from the community can contribute to jQuery. We are writing proposals, submitting the proposals to the jQuery forums, and revising the proposals in response to community feedback. The jQuery team can decide to reject or accept any feature that we propose. "
vkelman 34p · 784 weeks ago
Yes, I over-exaggerated :)
My concern, though is that MS has a long history of promoting-by-example of a very bad tight-coupled Win Desktop - like way of Web programming. And because there are so many developers who is using MS technologies (myself being .NET Web developer, C#, F# and MVC lover), there is a big danger of bad influence on those developers using jQuery as a part of their .NET work. Microsoft's approach on AJAX, AJax Toolkit (which was mentioned in that article) which heavily mixes .NET server-side code generation and client-side JavaScript, is insane. It creates incredible hard-to-understand code.
And no, I don't think MS would be able to impose bad design decisions on an excellent jQuery core team. (BTW, I see MS programmers' culture as becoming much better, more open ALT.NET - like, etc. )
Please also see my older "‘The WebForms Rant’ by karl Seguin" post and many excellent post by Karl Seguin at <a href="http://codebetter.com/blogs/karlseguin/default.as..." target="_blank">http://codebetter.com/blogs/karlseguin/default.as...
Lelando · 784 weeks ago
For example, while I, like most web devs out there, have an extreme distaste for their earlier (and might I say 'horrific') browsers, I also have to give props where props are due: they've recognized the error of (many of) their ways and are slowly but surely making good with their newer products. IE8, for example, isn't a huge P.O.S. like past versions... it's not perfect, but it's a *lot* better to work with and code for.
Thanks again!
Cheers,
Lelando
Lelando · 784 weeks ago
vkelman 34p · 753 weeks ago
vkelman 34p · 784 weeks ago
Regarding IE8: I basically have no complains against it (except the fact they didn't fix some small but old and annoying bugs http://pro-thoughts.blogspot.com/2006/10/incorrec... There was no way to submit error directly to IE team either. At least, I didn't find one). But it just doesn't want to work normally on neither my work machines (old Win XP and Win Server 2008 working inside Virtual machine), nor on my home machines (powerful and with freshly installed Windows 7). On both it takes enormous time to open, especially - to open new tabs. I didn't find a simple way to fix it, so I basically stopped to use it altogether, switching to to a latest Google Chrome 5 (dev channel version) with IE tab extension installed for some MS-specific testing.
Lelando · 784 weeks ago
Lelando · 784 weeks ago
vkelman 34p · 753 weeks ago
Read this article in Visual Studio Magazine: "Microsoft Contributes New Technology to jQuery" http://goo.gl/ppnA.
Again, Microsoft's own history of super-over-complicated AJAX.NET, of client side JavaScript code magically generated by server-side code in almost impossible-to-comprehend manner, of making simple things complicated makes me highly suspicious.
RamyaRagavi 29p · 291 weeks ago
MSBI Online Training | MSBI Online Certification | MSBI Course