Five Years Ago: Netscape Announces Intention to Release Source Code
Wednesday January 22nd, 2003
On this day in 1998, Netscape Communications Corporation announced that it was planning to release the Netscape Communicator 5.0 source code to the public. Heralding the move as "bold" and "aggressive", Netscape described how it intended to "create a special Web site service where all interested parties can download the source code, post their enhancements, take part in newsgroup discussions, and obtain and share Communicator-related information with others in the Internet community." You'll know this site as mozilla.org.
#22 OT, but I'll respond
Thursday January 23rd, 2003 11:27 AM
You are replying to this message
.NET is an improvement for developers in many of the same ways Java is. However, the things i don't like about .NET are:
1) Web forms are extremely bandwidth intensive. The entire state of the form is sent back and forth to the server wich can be like 30-100k per request (this is what I have seen anyways, and also depends on the form). You can roll your own mechanism to use session instead of the default implementation to trim down bandiwdth usage, but then you wouldn't be using WebForms, would you?
2) The API has changed between 1.0 and 1.1 in very incompatable ways: Classes have moved between namespaces, parameters are different, etc, and there's no way to find out of these changes except upgrading the framework and then watching your app blow up. At least in java you have a @depricated flag that will indicate that methods will be expired over time...
3) There are still many many aspects of the framework that resemble a Win32 wrapper. It would have been nice if they defined a nice abstract layer that sits above the win32 api instead of exposing it in the framework.
4) DBNull. 'nuff said.
5) The only tool vendor playing in .Net so far is Microsoft. I don't see a thriving community of competitive toolsets like we see with NetBeans, JBuilder, WSAD, etc, and I don't see too many deveoper companies feeling comfortable competing with microsoft tools.
I could also go into the relative problems in C# and VB.NET as well as 'Managed' C++, but why bother. It's a shame that talented developers are working on Mono so hard when there is so many other projects out there that are less likely to turn sour on the development group. Bookmark this response, because you can mark my words: The mono team _will_ be raped before this is all over. MS has a _horrible_ trackrecord for working cooporatevely with an outside organization.