> Now tell me what technological challenge FoxPro was to MS? None at all. It > was an old MS-DOS app ported to Windows, based on old DBase technology. > They > just wanted to get the FoxPro customers. And I think the same may be true > for Delphi. Apart from that I believe Delphi - or at least Pascal - would > be > interesting for MS, as it is a solid programming language with obvious > benefits compared to others. I assume I don't have to explain that to you > Delphians.
Rushmore technology came out of FoxPro. They bought it to get the technology to stuff into the Jet. That technology gave them the ability to support compound indexes and sped up other aspects of the WHERE clause. Later parts of that same system found its way into SQL Server and to my knowledge is still used (not in its entirety however). They bought FoxPro, ripped the query optimizing engine out of it, stuffed it into their products for an instant performance gain. FoxPro was well worth what they paid for it. That said, few people are clamoring for Pascal and if they were Chrome would be the obvious choice as it plugs directly into their already existing IDE and could be had for easily a 10th the price if not cheaper. To further my case, they decided to kill of VB "Classic" as it still had ties to Win32. What would the do with Delphi? It is completely against their current philosophy that backwards compatibility is backwards thinking. __________________________________________________ Delphi-Talk mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi-talk
