Beth points to this article
VB as a dynamic language which hints at good things to come post Visual Studio 2005. Strong typing vs. loose typing is always one of those "language war" type of scenarios and for that reason, I do like VB and Java. But the post goes on to talk about how MS will be integrating data into the language more "than ever before".
Which makes me stop and think "so why should a new developer go about learning to do things the HARD way in VS 2005?" Why shouldn't they wait?
It's a difficult decision. Some say "well because then you learn where you're coming from" and there is a certain attractiveness to that. Knowing how to lay bricks would also come in handy if I couldn't find someone to build my own house but part of the value of these development tools is that it's SUPPOSED to make it easier. Just as knowing how to ride a horse might be valuable if you ever had to do it, you typically don't need to because there are other modes of transportation available.
So if a current FoxPro developer was thinking of building a new database app in Visual Studio or Visual Foxpro today, knowing that Sedna will ensure the app would be supported in Longhorn for the next ten years - what is the reason to move to VS 2005 for a pure desktop application?
VB as a dynamic language which hints at good things to come post Visual Studio 2005. Strong typing vs. loose typing is always one of those "language war" type of scenarios and for that reason, I do like VB and Java. But the post goes on to talk about how MS will be integrating data into the language more "than ever before".
Which makes me stop and think "so why should a new developer go about learning to do things the HARD way in VS 2005?" Why shouldn't they wait?
It's a difficult decision. Some say "well because then you learn where you're coming from" and there is a certain attractiveness to that. Knowing how to lay bricks would also come in handy if I couldn't find someone to build my own house but part of the value of these development tools is that it's SUPPOSED to make it easier. Just as knowing how to ride a horse might be valuable if you ever had to do it, you typically don't need to because there are other modes of transportation available.
So if a current FoxPro developer was thinking of building a new database app in Visual Studio or Visual Foxpro today, knowing that Sedna will ensure the app would be supported in Longhorn for the next ten years - what is the reason to move to VS 2005 for a pure desktop application?
Comments