Microsoft Adding jQuery To Visual Studio 67
Tim Anderson writes "Microsoft's Scott Guthrie, Corporate VP of the .NET developer division, announced that the open source jQuery Javascript library will be integrated into Visual Studio, the main Windows development tool. Further, Microsoft will treat jQuery as a supported product within technical support contracts, and will use jQuery to build new controls for ASP.NET, its web platform."
Re:Scary (Score:3, Interesting)
The studio itself is fine. I don't think its built with a bunch of different technologies. Its basically C++. But the products it creates are patched together with all sorts of things. They give you sort of, "widgets" that you just drag in. They try to abstract whether the widget was made in visual C++, C#, Visual Basic, etc. But in the end, it can be important to understand what these things are.
You can make some really nasty quick and dirty stuff in Visual Studio. Sure if you are out to make solid code you can do that as well. But it can get frustrating as you have to keep smacking down the widget approach.
jQuery rocks, no comment on Microsoft (Score:3, Interesting)
Re:Microsoft incorporating Open Source? (Score:4, Interesting)
Because the jQuery maintainers are going to happily incorporate Windows-only modifications made by Microsoft to the library, correct?
Because "we'll be shipping jQuery as-is, and submit patches to it like everyone else" means something weird and wacky you must have deduced ahead of us. Correct?
Actually I'm at a loss here. Could you enlighten us as to how these evil tricksies will take place.
Re:Yet another Microsoft ripoff (Score:4, Interesting)
I really doubt that this is a case where extend and extinguish is really viable or intended. Its not like jquery is some fundamental piece of open source that it's destruction would advance ms in any way, as you note there are tons of other similar active great projects.
If they wanted to extinguish it then I doubt they would make it such a core piece of Visual Studio. It sounds to me like they finally realized how retarded visual studio was compared to what was freely available and decided to just integrate with a good existing project. If anything I think that in this specific area they plan on working with the community in a positive way.
so at worse I think we will see some unpleasant branching or the addition of some lame IE specific code. Its a rare case where one can say kudos MS! They integrated with a good project for the right reasons.
Re:jQuery rocks, no comment on Microsoft (Score:3, Interesting)
Whats the point of comparing this with Adobe Air? Adobe Air is to leverage your web programming skills (yes, including jquery!), to make desktop applications (applications that normally are impossible on the web...for example, one that needs to access local ressources). Its complementary to everything else, it doesn't replace anything.
For things like Silverlight, the goal isn't even the result the end user sees. Ignoring the joke that was Silverlight 1, the idea is to be able to reuse .NET code (or to some extent, .NET skills if you don't have any code to reuse) in a browser. If you don't have any already existing code to reuse, and you're just as good in javascript as you are in another programming language, then of course Silverlight is pointless.
Different problems, different solutions.
Re:Scary (Score:3, Interesting)
I love master pages, as the way they work is above and beyond what most other template systems offer. I like C# and
Silverlight sometimes seems like a solution waiting for a problem, but it's cool, and at least will scale with client growth. Silverlight + Dynamic Data (Astoria) is awesome, if limited to those with Silverlight/Moonlight installed. I don't know where development is going in the next couple years. I just hope that it doesn't all fall down.
Re:Yet another Microsoft ripoff (Score:4, Interesting)
I am one of the developers working on javascript support in VS. I am working very closely with jquery support. Our goal is to get as many developers as possible using our tools. That means supporting libraries that web developers want to use.
Re:Microsoft incorporating Open Source? (Score:3, Interesting)
People are nervous because we seen this pattern before on a non-open source (at the time) language/library. It went like this:
1. Incorporate JQuery into visual studio and add windows specific code to "enhance the productivity within visual studio".
2. Books and MSDN will refer to the Microsoft extensions as cool ways to get thing done in JQuery, and people new to the software will gravitate to the Microsoft version, colleges will teach it (most colleges use Windows in their labs), and since most people use windows anyway they see no harm in adopting the extended edition.
3. Continue to refer the extended version as JQuery, causing confusion between the Microsoft version and the official version.
4. JQuery loses enough share to the Microsoft version to cause some grief to the non-microsoft developers. Especially since a lot of enterprises are sold on the Microsoft method of IT, and would like their developers to take advantage of the Microsoft technology.
5. By the time damage is done and JQuery complains, Microsoft will rename their version JQ++
6. Eventually Microsoft will abandon JQ++ and move all new development to Query.net.
eclipse/netbeans (Score:4, Interesting)
Is there any similar effort toward building eclipse/netbeans/??? IDE's for jquery?