I really like what Microsoft has done with .NET. It really makes programming fun and easy. The only thing that bugs me, is seeing Microsoft tout .NET as a language-neutral platform. So far every .NET-enabled language I have seen has been altered to comply with the .NET platform. Keywords have been added to C++, OO features were added to JavaScript and we won't begin to talk about VB, COBOL and others. What is the benefit of language interoperability if all languages are the same thing? The truth is that the real advancement of .NET is not language interoperability, it is IL. By using an abstract Intermediate Language, Microsoft has added a new layer between the compiler and the binary. When you compile your source code, a .NET compiler will compile your source to IL. This is much different than a regular compiler, which generates low-level machine language. Since IL is a much more abstract than machine language, the result is obvious - languages end up looking similar since they all have the same base - IL. I'm not saying that language interoperability is a bad idea, I just think that interoperability should not be one of .NET's top 10 major selling points. Most developers will eventually catch on and realize that this interoperability was accomplished by adding an intermediate layer, and the term "language interoperability" may just be a nice way of saying "all .NET languages are the same thing". Microsoft should call a spade a spade. Joshua
J
Joshua
@Joshua
Posts
-
Language Interoperability -
Win2000 Ballons style tool tips...Does any one have a good tutorial or sample code for creating the new ballon style tool tips that are in win2000.
-
Reading delimited files...Thank you also Roger. This is exactly the help I was looking for. I works great. Joshua
-
Reading delimited files...Thanks for the insight. This is exactly what I was looking for, I just didn't know where to go. Thanks again for your time. Joshua