Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: Tenchusatsu who wrote (158812)	2/14/2002 5:47:06 PM
From: wanna_bmw	Read Replies (1) \| Respond to of 186894

Tench, Re: "what is C#, and why the heck would anyone want to use it over C++ or VB?" I believe it's a C++ type language, and Microsoft is pushing it into the industry with some mild success. Check out this link for more information. msdn.microsoft.com "More than anything else, C# is designed to bring rapid development to the C++ programmer without sacrificing the power and control that have been a hallmark of C and C++. Because of this heritage, C# has a high degree of fidelity with C and C++. Developers familiar with these languages can quickly become productive in C#." wbmw

To: Tenchusatsu who wrote (158812)	2/14/2002 6:00:52 PM
From: Joe NYC	Respond to of 186894

Tenchusatsu, what is C#, and why the heck would anyone want to use it over C++ or VB? Well, Java started from C++, and improved on it, making the job easier for programmer. C# is MSFT's own branchng away from C++. The main area of C++ bugs center around memory allocation, deallocation and management. It is programmer's responsibility. Pointers of C++ give little or no protection for programmer to screw himself (source of the famous General Protection Faults), and programmers do. Java and C# have their own memory management, use references, which are more restrictive than pointers, but the main feature is "managed code", that is the code is not really compiled to executable, but it is converted to an intermediary code that runs on top of the runtime (CLR in MSFT world, VM in Java world). Theoretically, someone can write CLR and .net framework for Linux. Other, non-MSFT languages can be converted to run under .Net runtime, etc. I have a feeling that MSFT finally got it right, after spending years in wilderness of ActiveX, COM, COM+. But it's going to take some time for .Net to become mainstream. Anyway, from hardware point of view, all MSFT (with help of CPU makers) need to do is to write and possibly optimize CLR for different processors, and suddenly, all the pure .net apps can run with reasonable optimization level on Netburst, IA64, x86-64, in addition to standard P5, P6, K6, K7 processors. These apps can still call native non-CLR DLLs just fine (except Itanium). Java was a bit clumsy in this regard (calling native code). I've heard of it before, but it sounds like yet another Microsoft NIH. Well, sort of. It takes the best ideas of Java, and supposedly expands on them. I have not played with C#, so I can't give you first hand account. Joe

To: Tenchusatsu who wrote (158812)	2/14/2002 11:39:42 PM
From: Dan3	Read Replies (2) \| Respond to of 186894

Re: what is C# C# is the result of Microsoft getting Anders Hejlsberg (who led the teams that created Turbo Pascal and Delphi) from Borland. Here's an interview with him where he describes what he was up to this time: windows.oreilly.com We're starting to use it - so far, so good.

To: Tenchusatsu who wrote (158812)	2/15/2002 2:22:20 PM
From: Charles Gryba	Respond to of 186894

Tench, C# is very close to java without the java jdk. It uses the CLR ( Msft's version of a jdk ). The whole .net project was headed by the guy who created borland's delphi so there are a lot of resemblance to that product also. C# runs managed code and does not allow for pointers which can cause crashes/memory leaks, etc. Msft commited to writing their products in C# so I see that language as eventually prevailing for any products running in Windows. VB.Net is significantly different from VB 6.0 where many VB programmers don't want to bother. I personally think VB's syntax is easier then C#'s and since both generate intermediate code that runs in the CLR hence with the same performance I don't see why anyone would want to bother with c# unless they are coming from the C++ and/or java world. C