Web 2.0, Meet .Net 3.0

An anonymous reader writes to mention an eWeek article about Microsoft's move to rename WinFX to .Net Framework 3.0. Microsoft has also announced the availability of the beta version of the MSDN Wiki, the company's first step toward allowing customers to contribute to Microsoft's developer documentation. From the article: "It is purely a branding change, company officials said. The gist of the issue is that Microsoft has two successful developer brands in WinFX and .Net, and the company has seen 320,000 downloads of WinFX -- and 700 signed GoLive licenses -- since the December Community Technology Preview, and more than 35 million downloads of the .Net Framework since the November launch. "

Comments

FROST PIOST

[Anonymous Coward]

SUCK IT WEINERS

Re:One-upsmanship

[jiushao]

Well, they were way ahead of everyone when it comes to the Web 2.0 stuff.

Re:Microsoft just seems to be kind of flailing.

[FyRE666]

This is pretty funny from my perspective. I'm a web developer and have recently been informed I'm going to have to start using .Net as some of our clients have decided they "must have it" (the fact they have no idea what it is, or why they need it is of course irrelevent). I'm a Java/PHP guy, so wasn't exactly over enthusiastic at this news. One of my main reasons for not wanting to get on the MS treadmill (apart from the obvious ethical reasons) was that locking yourself and your clients into one companys products WILL result in more expensive development, and less choice (which is what MS is all about).

Here's a prime example; one day code written against a framework will work. One "windows update" later, time to rewrite! Oh how I'm going to laugh!!! [breaks down into hysterical sobbing]

Re:Microsoft just seems to be kind of flailing.

[FyRE666]

You're definitely new to the .Net world and appear to have completely missed the whole existence of Mono which works with Apache on Linux. I believe other platforms are getting it soon as well but your statement is already out of date. A lot of apps will work in mono without much if any trouble. So where's the vendor lock-in exactly?

Yeah, I'm sure MS will be happy to provide the Mono developers with full documentation every time they make changes too. After all, they do help the Samba guys out all the time! Let's face it, they'll do everything they can to ensure that the only *stable* platform is .Net with IIS.

Hopefully you're correct regarding the seamless upgrades, so I'll see how it all goes. Personally I'm not enthusiastic about it at all, coming from a strong *nix, and open source background. I get the feeling that I'll end up another clock-puncher, and have no interest in my work in a few months...