Both sets of people can be present in the same company. There have been postings in the F# forums of devs wanting to use F# because they know it's good, but being very clear that corporate policy is going to restrict them unless certain conditions are met. Whether IP concerns from open source contribs is one of these, I dunno.
Nitpick: F# is really a multi-paradigm language. It truly does provide OO, functional, scripting and interactive styles.
> There have been postings in the F# forums of devs wanting to use F# because they know it's good, but being very clear that corporate policy is going to restrict them unless certain conditions are met.
Maybe the F# people should rename it "C# Functional", then the devs can write code in it and if the managers say anything, just tell them it's part of C#, and they'll be none the wiser.
Comments
Both sets of people can be present in the same company. There have been postings in the F# forums of devs wanting to use F# because they know it's good, but being very clear that corporate policy is going to restrict them unless certain conditions are met. Whether IP concerns from open source contribs is one of these, I dunno.
Nitpick: F# is really a multi-paradigm language. It truly does provide OO, functional, scripting and interactive styles.
> There have been postings in the F# forums of devs wanting to use F# because they know it's good, but being very clear that corporate policy is going to restrict them unless certain conditions are met.
Maybe the F# people should rename it "C# Functional", then the devs can write code in it and if the managers say anything, just tell them it's part of C#, and they'll be none the wiser.
Someone here had a good way to do this (sorry, my google-fu is not strong enough to find the link):
"What language do you use?"
".Net"
"Oh, OK"
there seem to be a lot of interop issues with C#
http://www.ctocorner.com/fsharp/book/ch17.aspx