Re: Re: Re: Re: Re: Why do people think MSSQL is any good, anyway?
Originally posted by ryan
Yes, .NET like a lot of MS products is very nice but how can you use it and feel good about what you're doing? By using Windows/IIS/MSSQL/.NET you've locked yourself into closed, proprietary technologies that are controlled by convicted monopolist and are at the mercy of that monopolist.
Please. I've been through anti-MS FUD. 99% of those are unfounded. Of course 78.4% of statistics are made up.

But you get my point. Most of them are just outright ridiculous.
I use Microsoft .NET and feel good about what I'm doing because Microsoft .NET allows me to code less, quicker--basically be more productive. As a programmer, that is very important. .NET can be very versatile, even more so than Java sometimes.
.NET is Microsoft's highest quality software architecture ever. They spent years and years reimplementing Win32, COM/COM+, ActiveX, etc. into one nice package in a managed environment.
Sure Windows and and IIS are proprietary. But what do I care. They work, and they do work very well. They sure as hell are much easier to use and configure than UNIX servers with Apache and they are just as stable and work as well.
And what are you smoking about Microsoft SQL being proprietary. It's using ANSI-SQL for pete's sake. Every piece of SQL queries and stored procedures has worked cross platform with PostreSQL, as I do development on both PostreSQL and Microsoft SQL Server. SQL Server 2000 also can export the requested query to XML. All standards. Okay, maybe not ADVANCED features. But same is true with Oracle. Playing devil's advocate: Oracle *IS* proprietary as well, yet you drool over Oracle, just because it's not Microsoft's. SQL is pretty much compatible with any others, except on extremely advanced stuff. MySQL b0rks out on some ANSI SQL that I've tried, but then again, its target isn't enterprise, but as a fast engine for the Web that people can afford if they can't afford or don't need the advanced features of all advanced SQL database servers.
Oh, by the way, .NET isn't exactly proprietary. It's Microsoft's implementation of the ECMA standard CLI. As with Java, .NET classes can be proprietary (i.e. System.Windows.Forms) but there is nothing to stop Mono from being able to implement their own. In fact, they have a few that binds with QT and GTK. Hell, I can even make 100% pure .NET binaries using Mono with GTK to produce Linux UI apps without a single cent sent to Microsoft. This is similar to Java's Swing. Apple is doing exactly this--keeping the UI proprietary. So suddenly, for Microsoft, this has to change? Wtf. In fact, I think this is the best way for UIs to interoperate. Why should Microsoft bother optimizing Windows Forms and make sure they work on all of X11's Window Managers. GTK and QT already can do pretty much what is needed--all they need is a .NET wrapper for it and optimize it. I'd choose that for a Linux solution over trying to make Windows Forms work on all window managers.
At least it's finally pushing competition to Java. Sun will have a much greater incentive to innovate on Java.
Please, send your FUDs to people who will blindly believe you. I know for a fact that I'm not the only .NET developer surfing on this boards.