Programming languages: C# versus F#, building AI and Physics

Programming languages: C# versus F#, building AI and Physics

  • Comments 2
MagazineHorrorTales0371

There are two computer languages that can be easily be used on the XBox 360: C# and F#

In game design, and certainly shared source games like MechCommander are a great way to investigate the architecture of a professionally designed game. 

Dreamspark gives students access to the Game Studio 3.0 resource that allows you to transfer games you designed on your PC to your XBox 360 and play them with your friends or even sell them on Community Games.  C# is a really good deal, you can design and build cool games using only C#.

So why would you use F# to build games?  F# is different from C#, F# is designed to support scientific and engineering.  With games, you might find it easier to do the physics of a game if you use F# rather than C#.  C# would support the view and perform control of the application, but in some cases the physics programming is simpler if you use a language like F#.

These are the kinds of things I think about.  Maybe I should lighten up.  Naw.

Ok, I think that we will start to use F# to build Finite State Machines that can be consumed by programmers.

Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • What does C# have that makes it more ideal to the tasks you mention? Or, what does F# lack (besides designers) that would make it something only to use for the physics?

  • This is a great question, but not one that is easily answered in a short comment.  I will be working on answering your question over a period of time.

    For now my answer is that F# is designed to be used for scientific, mathematical and engineering types of efforts.  C#, as well as Java and other imperative languages are not as well designed.  But I have not offered evidence yet to support that have I?  So this is one of my goals.

    Thank you.

Page 1 of 1 (2 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control

Restrictions:

  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them