".NET's 18,000-Mile Checkup" [via Scobleizer]
I'm still primarily a C++ programmer. .NET seems to be primarily about webservices and I have yet to have occasion in my work to require communicating to webservices or needing to expose functionality through a webservice. I expect I will one day but that day hasn't come.
... as .NET developers write less code and spend more time “uncovering” components in the framework and mapping those components to business processes, the role of the application developer is changing.
I don't work with business processes either. I write consumer-oriented software. Don't do much business programming. Not to say I wouldn't target the enterprise, but even there it will probably be some communication/productivity tool. That's just the nitch that I swim in.
"Because VB.NET and C# are so similar, in effect the framework is the language itself, added Janacek. "How you structure an IF statement is minor compared to what that IF statement accomplishes through the framework. The language is deprecated, and the framework is elevated."
"...the actual experience of working with .NET is all about navigating the framework, not writing code."
I don't understand these statements. Is it hyperbole? It's as if it's saying the application you undertook to write is sitting there somewhere in the framework and it's up to you to discover it; no new code needs to be written. Perhaps if I was emersed in .NET the statements would make sense, but since this isn't likely to happen can someone explain this to me?
Setting aside what everyone else is using .NET for, I'm sure there is a lot .NET can offer me but three things prevent me from making the leap.
1. Requiring everyone have the .NET framework installed. I know, I know, soon everyone will have it preinstalled but they don't today
2. Existing codebase. I don't have time to stop development and port ALL my code, and I don't think my codebase lends itself to porting piece-meal
3. The learning curve.
11:45:11 PM 
|
