After a long battle with technology,=?ISO-8859-15?Q?Sven_K=F6hler?= <[EMAIL PROTECTED]>, an earthling, wrote: >>>That still true, but it Mono might become a good choice for cross >>>platform development too, although that might take some years. >> Well, C# and .Net is going to be windows only and almost >> exclusively microsoft backed, so if you think you are getting cross >> platform capabilities like Java or Perl, think again, it's going to be >> more like the cross platform capabilities of C when you use a lot of >> binary only liberaries. > > It's a bit OT but you just said .NET was "invented" my Microsoft, you > didn't tell anything what you expect for Mono's future. I hope it > odesn't get forbidden due to any software patents. > BTW: ODBC was invented my MS to (i don't know for sure, but i'm about > 99% sure), and it's going to get popular for UNIX too.
Bzzt. ODBC was what Microsoft decided to rename SQL-CLI to when they republished the standard as if it were their own. http://www.jcc.com/SQLPages/SQL%20Part%203%20SQL%20Call%20Level%20Interface.htm "The SQL/CLI is a programming call level interface to SQL databases. It is designed to support database access from shrink-wrapped applications. The CLI was originally created by a subcommittee of the SQL Access Group (SAG). The SAG/CLI specification was published as the Microsoft Open DataBase Connectivity (ODBC) specification in 1992. In 1993, SAG submitted the CLI to the ANSI and ISO SQL committees. (The SQL Access Group has now merged with X/Open consortium.)" And the notion that .NET was "invented" by Microsoft strikes me as indicating a whole lot more "inventiveness" than they are traditionally noted for. I haven't yet perceived anything about .NET that is sufficiently novel such that the term "invented" would seem applicable. It's pretty much another run-of-the-mill P-Code reimplementation, looking more like a rehash of J2EE than anything else. Oh, it has APIs for all sorts of Windows-only services. _Sure_, that's inventive... >>>Well, you're using ODBC, and i guess Stephen can't use ODBC any more >>>since it is poorly supported by .NET ... >> Then maybe he shouldn't use .NET? > > What an arrogant position. It hardly seems an arrogant position to suggest that if .NET is deficient in vital ways, it may make a poor choice as an application platform. -- "cbbrowne","@","ntlug.org" http://www3.sympatico.ca/cbbrowne/finances.html Obversely, a lot of verbal mileage can also be gotten by sending out incomprehensible, cryptic, confusing or unintelligible messages, and then iteratively "correcting" the "mistaken interpretations" in the replys. -- from the Symbolics Guidelines for Sending Mail _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
