smoothdeveloper

Curious what are the curly-bracketisms in F#?

Not sure about exposing Swift to C itself, while Rust has a clear "call from C" story.

I think that's what was referred to.

you can get around the login wall with http://bugmenot.com/

You might be right about a small subset of people, but most developers using languages like ruby, python, basic, pascal, etc. would prove this wrong.

Also most of F# are fairly well experienced C# programmer, and I think they do find the language compelling.

It is still a long way before:

* pattern matching / active patterns

* Discriminated Unions and many other crucial type system enhancements over POCO in C#

* real functional orientation (function composition, immutability by default, partial application)

* type providers (it is not necessarily about data provider)

* more compile time safety harness

* plenty of other things that become apparent when you get comfortable with the language

C# 7 is still doing catch-up with F# 1.

My hypothesis is that it is easier for many people to not try too hard to grasp at functional programming or just learn a new language.

My hypothesis is that other half says:

* Code is less clear than C style (type inference, not used to some pervasive operators like function composition or piping)

* Code is terse and short names are more prevalent (Lost the way to kingdom of nouns)

* There is no Resharper support, and Visual Studio (the main IDE with F# support) tooling is not as advanced as for C#, which is impairing to some extent if you look use the language like a glorified C# and not too used to F# way (tooling is great compared to many other languages IMHO)

* There is no do/while or goto or break

I'd say yes if you have exposure to Java library & ecosystem, because .NET Framework's Library has a similar flavor to Java Standard Library.

There are also a bunch of F# centric projects (http://fsprojects.github.io/) which might help you to stay in mostly functional programming land and not mingle too much with OOP.

The main difficulty is to get runtime working well, I think Mono has come a long way and is now well packaged and stable enough to get a good experience of the language, thanks to Xamarin who really invested a lot of efforts.

Microsoft is allegedly working on its open source implementation of .NET Framework and runtime, which just landed official F# support, but I think right now the experience and eco-system support has catch-up to do with what can be done with Mono.

Hope this helps!

2015 survey results https://docs.google.com/forms/d/1Ly_W1ZUH3x_ph4H6I_64uvEib2b...

I hope there will be more submissions this year!