Vivek Thakur

Chaotically Complex

  Home  |   Contact  |   Syndication    |   Login
  102 Posts | 1 Stories | 317 Comments | 66 Trackbacks

News



Archives

ASP.NET Ventures

I was reading about LINQ and though it is a really nice technology but there is one big problem which has been cropping up in my mind since quiet some time:

New technologies are coming at a much faster rate than developers can absorb.

LINQ, DLINQ, Windows Communication Foundation, SOA (though this is related to Arch)...

Developers today even face problems writing efficient code in ASP.NET 1.1, forget about framework 3.0. And if things keep coming up, no one would know what to do next...learning curve is not that easy for all these technologies and people often end up using the technology in a wrong way.

.NET 2.0 framework is still maturing and there are news of version 3.0 being released later this year. Though 3.0 is just a wrapper around 2.0, problem is that words like WCF, indigo etc make developers feel like they are left behind unless they do projects using these technologies. I strongly feel that all these new technologies will add to confusion more than really help. Who would take time out and learn these new technologies well enough to know the pros and cons in order to use them effectively? And even if someone does, by the time he or she is over, 10 new technologies would have replaced them.

Things need time to mature ..this is all I can say..

posted on Thursday, August 31, 2006 2:33 PM

Feedback

# re: Developer's NightMare 9/1/2006 8:41 PM aliem
agreed fully... the pace at which new frameworks are coming out is too much. The amount of time you have to spend on R&D is taxing on developers and the company.

The bigger issue is when new tools like visual studio 2005 come out and force you to use .NET 2.0. I'm glad it forced me to shift, but at the same time it's a pain.

# re: Developer's Nightmare 9/13/2006 11:31 AM Dheeman
It's right to some extent , howeever I do not agree to it fully as most of them are enhancements to their earlier versions, which does not cause a lot of problems to developers. The biggest problem comes when something absolutely new comes up and replaces the old one , like what .NET did to vb6

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: 
Please add 7 and 6 and type the answer here: