Environment versions
Network:
Windows 2008 Server
>Joel
>
>I've made this speech before, and I'll make it again... sorry.
>
>I am really upset with the fact that MS has provided no migration path for a discontinued VFP. They could have easily spent some time making the transition to .NET a little easier by providing a conversion program for forms and reports. A google search will return an app that supposedly converts VFP forms. Not sure how good it is, but MS should be the one providing this tool.
>
>What guarantee do you have that MS won't dump .NET for the next "great" platform when they feel like it and then where does all your .NET experience go? I'm a realist, so I really don't expect that to happen, but I really didn't think MS would dump VFP without some kind of a migration to something. They really set us up...
>
SNIP
>
I fully expect Microsoft to replace .NET with something different some day, or change it enough that it's like a different technology with the same name (a la FoxPro and Visual FoxPro). Given all the effort MS has put into .NET and the number of developers / shops now using it, I don't expect that to be for a while, but it will happen. That is the nature of this business. The days when a software developer can use the same tool(s) for their entire career are gone, if they ever truly existed. Personally I like it this way. I wouldn't want to do the same thing for 40 or 45 years.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only