Last week, Microsoft dampened relations with its developer community by revealing changes to its MSDN (Microsoft Developer Network) subscription service and releasing different editions for its Visual Studio 2005 development tool.
This follows the recent petition by more than 200 of Microsoft’s own MVP (Most Valuable Professional) members and thousands of developers to urge Microsoft to continue the development of the older version of Visual Basic, and help preserve their investment in existing applications.
Licensing changes to MSDN was meant to simplify the structure and give smaller companies access to the service but the negative response has been clear -- the new pricing structure is too costly, according to some of Microsoft’s core supporters, Independent Software Vendors (ISVs) and consulting firms.
As Microsoft moves into the “application lifecycle tools” market, which address different phases of development typical in enterprise software development, the company hopes to make the full set of Visual Studio Team System a premium on top of current the MSDN Universal subscription.
Many developers have been disappointed with the lack of upgrades and new products from Microsoft over the past year, including service packs to the current Visual Studio 2003 release, but making MSDN subscriptions less valuable can only be a slap in the face to some of its staunchest supporters.
Microsoft's response to this is that Team Studio is meant for medium to large enterprises and not small shops. It claims its pricing is fair when compared with IBM and Borland.
However, as the company aims for further enterprise acceptance, it could short change its own developer community by selling what can be called crippleware to smaller, yet influential players. The effect of this could see a flock of developers move away from Microsoft’s tools and platform.
For lessons, Microsoft only needs to look at the aftereffects of Red Hat’s move away from its developer and early adopter communities to focus instead on enterprise customers. The developers left in droves, and are now known as “Red Hat refugees”.
With a large amount of ISVs in Australia, many developers will be keeping an eye on Microsoft Australia’s plans for local pricing. As one customer told an MSDN product feedback forum recently, "The success of Microsoft developer tools has been built on the back of independents like us that evangelise about their effectiveness in the large enterprises".
The ball is in Microsoft’s court.







1
Karl E. Peterson - 29/03/05
Unilateral declaration that developer's ****ets (source code) are disposable will certainly come back to haunt Microsoft for years to come. Any developer concerned about this owes it to the community to read, and consider signing, the "Support Cl****ic VB!" petition -- http://cl****icvb.org/
» Report offensive content
2
mappin - 13/04/05
Well Isnt The . Net framework supposed to support any language???
maybe someone will write a vb cl****ic compiler for .NET
The in the meantime for those of you that wrote code in VB6 and have been left hi and dry you shouldnt be surprised at all.
When VB went from 16 bit to 32 bit the same thing happend and there was exactly the same problem ... with backward compatbility.... or have you all forgotten the VBX -> OCX night mares
Funny though, it was about that time that Delphi suddenly became hugely popular... because Delphi developers had no such upgrade issues..... (and it was way superior)
Its pretty sad that MS managed to spread so much FUD that delphi began to fade away....
Interestingly Borland has just released Delphi for .NET 2005 and with minute adjustments (mostly conditional compiler directives) all the delphi samples recompile in .net pretty much with out fuss....
http://www.borland.com/delphi/demo/tutorial/tutorial1.html
So those guys still smart enough to make their own choice and use delphi... can now
compile to either
Native win32
.NET
Native Linux (in many cases).
All from the same source code
All from the same IDE
All from the same Components...(delphi components are written in delphi)
Eat your heart out. :)
» Report offensive content
3
FSD - 10/12/05
Who cares......things change, progress, and/or evolve... suck it up and move on. If M$ wants to do away with the vb6 let em...pick up a new language....delphi 2005 supports both delphi.net & win32 delphi apps however I read somewhere it wont be .net 2.0 complient till Delphi 2007 comes out.... Besides ditching vb6 might deture 12 yr old kids from writing crap programs that kick people off chatrooms ...god forbid if they would have to learn a real programming language....If you just HAVE to use VB ... learn .net and use mono and/or sharp develop
http://www.mono-project.com/Main_Page
http://www.icsharpcode.net/OpenSource/SD/Default.aspx
.....screw microsoft
thats just my opinion,....sorry I just dislike MS. lets see how much hate mail i get for this :D
» Report offensive content