لطفا منتظر باشید ...
.NET: The Future of Applications Development
Those who know me well know that I'm not a bandwagon person. I don't chase after the latest fads and never have. When Java first came out, I didn't join the party immediately. I waited for the hype to settle down a bit, then explored Java for myself and drew my own conclusions regarding its usefulness. When Linux first began making headlines, I didn't spend much of my time trying to use it or find tools that would allow me to build software for it. And when XML became all the rage, I waited until some of the standards settled down a bit before I made my first foray into it. That's just the way I ama little conservative, perhaps, but it has served me well.
So, when I tell you that Microsoft's .NET initiative is going to change the way that applications are built, you can assume that I thought a lot about the statement before I made it, and that I at least believe that what I'm saying is the truth. I believe that .NET will transform Web applications development from a haven for hackers to a place where software craftsmanship and sound engineering can flourish. A good number of expert developers have stayed away from Web development because it's such a revolting mess. I think .NET will change this. The best developers in the world will be attracted to Web development with .NET because it will feature tools and technologies that finally make sense, that don't feel half-baked, and that provide the power and flexibility that experts demand.
I believe .NET will especially be a boon to novice and intermediate developers. I believe it will keep rookie coders from shooting themselves (or their customers) in the foot quite so often. I believe it will protect us from ourselves while our development skills improve over time. It will make the easy things easy and the harder things only incrementally harder. It will alleviate the need to master ten different technologies just to build scalable applications, and will allow us to focus on solving business problems rather than on the trivialities of constructing programs.
