> I seem to remember that the Fox group was telling us that "fitting" VFP into the
> .NET framework would have severely crippled it. Anyone else have more
> information about this?
I think it's pretty straight-up, Chet. For MS to fit VFP into the .NET framework would involve a significant improvement to .NET that MS doesn't want to make.
While I don't spend time comparing languages to each other, my gut feeling is that all modern day 'high level' languages offer OO design and similar features, albeit with different syntax. For the most part, but I don't think converting from one heavy-hitter language to another is that big a deal, except when it comes to the database engine, which MS obviously doesn't want to endow .NET with.
However, the good news is that competition is bearing down on MS, notably in the form of Linux, and that may well "inspire" MS to become more competitive. If/when that happens, MS has VFP in it's bag of tricks that it can (finally) pull out the stops on.
Bill
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
©2004 William Arnold |
