Re: My thoughts on C# and gaming.
Jon Frisby <[email protected]>
| Newsgroups | gmane.games.devel.sweng |
|---|---|
| Message-ID | <[email protected]> |
On Jan 28, 2010, at 2:00 PM, Emil Dotchevski wrote: > On Thu, Jan 28, 2010 at 10:56 AM, Brandon Van Every <[email protected] > > wrote: >> On Thu, Jan 28, 2010 at 1:54 PM, Richard <[email protected]> >> wrote: >>> >>> In article <[email protected] >>> >, >>> Emil Dotchevski <[email protected]> writes: >>> >>>> C# is just a better Java, [...] >>> >>> Well, I definately disagree with that. Having been programming on >>> Windows for a decade, I see .NET as COM 2.0. If you look >>> carefully at >>> all the things in the .NET runtime, you can trace their development >>> back to COM. >> >> Why is that a disagreement? C# is a language standard. > > Richard has a point, C# and .NET are inseparable. The reason why C# > exists is to push Microsoft corporate interests by locking vendors' > code in the .NET prison. > > This also answers Richard's disagreement. That you can trace .NET > functionality back to COM is not an important differentiation. C# and > Java are not programming languages, they are proprietary platforms. Of > the two, I think, C# is the better one, that's what I meant. It is worthwhile to note that those of us who use Unity wind up getting a rather different "view" of C#, since by and large, remarkably little of what we use it for involves the standard libraries. There's the collections (generic and/or non-generic of course), and a few things like the Serializable attribute that are used all the time but everything else seems to follow a pretty sharp falloff in usage. File I/O is useful to some (but less than you'd expect due to how Unity is designed), XML parsing is useful to others (but a lot of us wind up using a totally different XML library that's not part of the .Net API to avoid bloating webplayers and the like), but generally speaking most of our needs get covered by the libraries Unity itself provides and venturing out much beyond that tends to be done as the exception rather than the rule. As such, the COM heritage tends to fade into the background. The C# language, in short, isn't as deeply or fundamentally tied to the .Net APIs as you seem to believe. -JF _______________________________________________ Sweng-Gamedev mailing list [email protected] http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com