Well, mostly tools. Also as I said, OO in F# is a a bit tedious to do in my opinion and the ASP.NET and ASP.NET MVC are very object oriented and were designed with imperative languages (primarily C#) in mind.

There's nothing in functional programming that prevents it from using in "typical web" apps though, as demonstrated by the engine that runs HN, news.arc, for example.

Out of true curiosity, what do you find tedious about F#'s OO support? Lack of protected?

Well nothing major really, it's just small bits here and there that are telling signs that it's a functional programming language with OO support and not the other way around. Like that you have to put two types that depend on each other in the same file.

No showstoppers, just minor annoyances that add up over time so when I write F# code I try to limit OO code to interfacing with other libraries (and the framework). Maybe it's just me, perhaps other programmers don't find OO in F# tedious at all.