Interesting analysis.

>Of course, as I point out to Craig in another post, .Net of today is not the .Net of 2001. Languages being created on the .Net of 2010 could not have been developed on the .Net of 2001, and only with great difficulty on the .Net of 2005.
>
>To think that .Net consists of C# and VB.Net (and maybe F# for the functional static programmers) is to miss the point of how .Net has evolved in the past 5 years. The speed difference between static and dynamic languages is basically eliminated by innovations in the DLR, based on real-world testing. So now it's down to what language does the job better for a given individual, in a given context: there is no more straight-jacket.
>
>The predictable result (from systems theory) is that differentiation in languages will lead to consolidation into sub-species. It will be interesting to watch over the next 10 years to see what language emerges in the dynamic + data sub-species.
>
>Hank
>
>>>>Or perhaps some developers are still holding on to old technology (VFP for example) because what could/should be considered new technology is already old technology. (.net for example). Who knows perhaps MS is close to announcing the replacement for .net. So those hanging on to VFP (or whatever) didn't have to suffer learning something what they didn't absolutely needed. Or something that they could hold on to just enough to not being forced to go the .net way.
>>>
>>>They're typical humans. Resistant to change.
>>
>>>
>>>>
>>>>Or better while resisting the temptation to jump too soon to .net, serious alternatives could be considered. I went to a WinDev demonstration recently and I was very impressed. I was happy to see that I'm not the only one to think that developers shouldn't do that much typing. I am not that thrilled when I go to .net meeting and see all that XAML one has to type before things look good.
>>>
>>>Too soon? Check you calender. .NET was released in 2001. You don't have to do ANY typing in XAML to make things look good.
>>>
>>>>It should be about time now that MS releases the new (Now we really have a good development environment) to the masses. This way they'll get tons of cash because what we used before is not good anymore and we will have to re-engineer those apps.
>>>
>>>What exactly are you looking for in an IDE?
>>>
>>>>
>>>>I can't wait to see that new development environment designed entirely for Cloud development. You say (or think) .net can do it. Perhaps too naive. I'm sure MS has something coming for that. But they won't probably release too soon. They have to make sure that others waste a lot of time with their old tools and then MS will release it. Don't forget that MS is also doing consulting. Cashing on all sides all the time.
>>>
>>>You can do cloud development today with VS. And you don't need to relearn everything to make it work. You work locally, which means you can debug. Then release to the cloud.
>>
>>Do you think that .net is the end of the line in development environment coming from MS? Nothing will replace it forever? The perfect paradigm?