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 : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?

To: Dave who wrote (54780)	1/1/2001 10:49:52 PM
From: Harvey Allen	Respond to of 74651

Microsoft .NET vs. J2EE: How Do They Stack Up? Even if you don't write code dedicated to Microsoft platforms, you have probably heard by now about Microsoft .NET, Microsoft's latest volley in their campaign against all things non-Windows. If you've read the media spin from Microsoft, or browsed through the scant technical material available on the MSDN site, or even if you attended the Microsoft Professional Developers' Conference (where the .NET platform was officially "launched"), you're probably still left with at least two big questions: What exactly is the .NET platform? How does the .NET architecture measure up against J2EE? And, if you think more long-term, you might have a third question rattling around your head: What can we learn from the .NET architecture about pushing the envelope of enterprise software development? java.oreilly.com

To: Dave who wrote (54780)	1/2/2001 4:54:01 AM
From: dybdahl	Read Replies (1) \| Respond to of 74651

C++ isn't used that much in GNU/Linux. The open-source movement have put it very much to display, how many serious problems C++ has compared to C. I don't want to start a discussion on C versus C++ here, I just refer to the big discussions that have been in the Linux world. One of the big issues have been binary compatibility between different compilers. This is probably going to be solved now with the GNU compiler collection version 3, but in the Microsoft world, it's still only C that is supported in DLL API's. If you want an object oriented DLL, you have to support the COM/ActiveX standard, which is incredibly slow and a big overhead. Additionally, languages like Java, VB, Delphi, C#, C++ builder etc. will take over where productivity is more important than using the ANSI C/C++ standards. C/C++ will always exist, simply because there is so much code in it. My local baker (!) even has a $5 book about programming Fortran!!! I was really chocked when I saw that. It is intended to a general audience and was made in a series of books with "How to use a scanner", "How to use Word 97", "How to make a presentation using Powerpoint" etc. Some things never die. C++ is a dying language in the market place. The percentage of programmers using C++ will drop so low, that is will become a minor language. Borland Delphi hasn't failed in the market place. C# is the closest Microsoft ever had to Delphi, if just they provide a good GUI toolkit. The speed of C++ and the ease of Visual Basic will draw the attention of many VB programmers, and maybe also some C++ programmers. It will never dominate any market, simply because it is made by Microsoft. But it will be a good tool for quick-and-dirty projects, and there have been many quick-and-dirty projects that have grown to enormous size, like Windows. :-)

To: Dave who wrote (54780)	1/3/2001 11:07:08 AM
From: Valley Girl	Read Replies (1) \| Respond to of 74651

My 2 cents: Java: MSFT is making a big mistake by not embracing it. It's already too late, Java is quite successful as a server programming language. MSFT's OS monopoly is mainly on clients. MSFT should view the browser as the "real" client and try to leverage their leadership position with IE. It's true that Java, among many other things, is helping to block MSFT's extension of their monopoly to servers as well. Well, too bad - they should stick to their knitting IMO, as they look like they're losing the battle client-wise in the growth areas (set-top boxes, handhelds), and this is their bread and butter, eh? C++: C will be around forever as the language of choice for most non-application-level code (like system code). What's "dead" is the whole OO/C++/MFC phenom - app programs have shifted to web-based technologies. OO types are much better off using Java than C++. System programmers don't use C++/objects and would go into apoplectic fits if they came near MFC. C# We all agree, this is a terrible idea. The world needs another language like, well, you know.