There are many small problems even with un-managed C++ under VSN.NET. It'll be a year (or two) before the CLR environment is running well. I wouldn't commit development $$ to it for a while. Ever tried to use the MS Transaction Monitor? A horrid MS mess, right up there with DCOM, which *never* worked right. Look how many years it took them to get the database libraries working right (remember the first few versions of DAO)? So, based some years of experience w/ MS product cycles, I would go slow on CLR.
Also, there isn't really room in the market for two OO, interpreted language infrastructures. It's much more than just the language itself. Historically, VB has filled a different niche: quick and dirty in-house apps.
Personally, I would recommend LAMP as the way to do web development. I only wish you could get Perl to let go of memory (all the way to the OS) sometimes. As it is, Perl code must be short-lived and is, therefore, inappropriate for many server-side uses.
Btw, WebSphere runs much, much faster on Intel/Linux than Solaris/Sparc. No idea why, tho. The real action on scalable computing is all happening on Linux as well.
take it easy,
Charlie
At 03:47 PM 11/5/2002 -0500, Erik Price wrote:
On Tuesday, November 5, 2002, at 02:33 PM, Charles Reitzel wrote:None of the .NET CLR languages are standard, either de facto or de jure. If you really want a Unicode-based, byte-code interpreter with garbage collection and reflection (and many folks do), just use Java.
I like Java and I'm all for any non-M$-only tech, but ...
http://www2.theserverside.com/home/ thread.jsp?thread_id=16149&article_count=690
_______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
