We'll be addressing this and other concerns in the next Community for F# Live Meeting on November 29. Please join!

If you want first-class metro support I suggest you vote on this link:
Metro development from F# without the need for C# assemblies and spread the word about it.

It's a shame that when the media talks about Windows 8, WinRT and Metro they act as if F# doesn't exist, all you hear about is JavaScript, C#, VB.NET and C++ but F# is nowhere to be seen.

This is very very bad for the mainstream adoption of the language, since Metro is the biggest part of Windows 8 and F# should be a part of that hypewagon.

IMO F# is the only true General Purpose Multi-Paradigm language on the .NET platform, 3.0 even added auto-properties with initial values that beat C# at it's own game, mutable classes.

We should vote to get first-class Metro support for Windows 8 to avoid F# getting relegated into 1-trick pony land.

In his talk a BUILD, Don said that it would be possible to use F# in a Metro app but in the context of a C# or VB front end project. The question here is would it be possible to develop and end to end Metro application with F#? In Metro apps content is king and content is data. With the addition of type providers F# is now THE language for manipulating data. I hope that F# will catch on and that we wouldn't get an F# Metro template project (that doesn't work) 9 or 10 months after the launch of Windows 8.