Is Microsoft Pushing too much, too quick?

I often find myself exhausted and frustrated not getting enough time to know every thing happening in the .NET world. There is always something new.

 

Since the launch of .NET 1.0 in year 2000, the .NET development has gone through several phases. So far, we see versions 1.0, 1.1, 2.0, 3.0, and even 3.5 is knocking the door. Besides these final production releases, there are CTP, Beta 1, Beta 2, and other versions. As a technology enthusiast, I try to keep up with Microsoft but there is a point where enough is enough.

 

Most of the companies are still developing on .NET 1.0 and 1.1 and .NET 3.5 is already here.

 

Other problem with .NET is, if you compare .NET 1.0 and 2.0, it’s just not an extension. Almost every thing is changed. And if you compare .NET 2.0 and 3.0, it applies here as well. So it’s more or less restarting on a new product again and again.

 

I don’t have any problem with a new version each year but I do have a problem when the version I just finished is totally wiped out in next version. If you compare a Beta 1 version and final production version, you will find most of the things don’t work in the final version.

 

It seems like CTP and Beta 1 versions are pretty much junk versions of the product and Microsoft try to get as much as possible feedback from community leaders, MVPs, authors, trainers, developers, and other users. But do they (Microsoft) really care for developers, their efforts, and their time?

 

I personally think Microsoft should slow down little bit after .NET 3.0 and let us (developers) settled down couple of years and bring any thing new to the table after every thing looks stable.

 

What you think?
Next Recommended Reading Microsoft.NET and JIT

Mindcracker
Founded in 2003, Mindcracker is the authority in custom software development and innovation. We put best practices into action. We deliver solutions based on consumer and industry analysis.