before yesterday I gave a talk at the User Group Cologne on F #. There, I've my experience with F # talked and showed some language features. Unfortunately, 30 minutes were a lot of shows too little of everything and also to answer questions. In the coming posts I will, therefore, my experience with F # record in writing.
F # is a new programming language in the. NET family. This is # in VS2010 VB and C in addition to one of the main languages for the development of NET,. According to the plan.
deja vu
When I first opened the Beta 1 of Visual Studio 2010, I had a deja vu experience. F # I had already tried it in VS2008, but VS2010 until I realized what Microsoft since has imagined. And he ran shivers down my spine. . Because when I installed for the first time about 6 years, visual studio 2003, to learn NET, stood next to VB and C # programming language to choose another, and that was J # .
J # Which way is gone, I need not mention. (Who still actively programmed in J #, let him not hesitate to contact me). Would suffer the same fate F #?
vs J #. F #
The question is whether pre-installed just because F # in VS2010 already and it does not have to download separately, then this is also often used. In J # which has of course not helped.
Well, at first sight F # a bad "karma." Why can we say but that F # will make its way?
| J # | C # | F # | |
| paradigm | object-oriented object-oriented |
| functional |
| language family | C | C | ML |
| compatibility | JAVA | - | OCaml |
comparison of J # and F #
The comparison shows that J # and C # are just too similar to that it would bring any real profit. Who wants to program in Java that makes Java and not with J #. Especially as it is with Eclipse has a much better development environment. F # has nothing to do with the other hand, C #. The language is based not on special on C ML (Meta Language). The type of programming is different, namely functional. Microsoft, however, with F # a few concessions made. F # refers to itself as "multi-paradigm" programming language, as opposed to pure functional programming languages like Haskell. We can define F # object-oriented class libraries that can be accessed by others. NET programs.
Conclusion
F # J # I can not be compared, even though it has many similarities. Not in the kind of syntax, but in the way F # is placed marketing point. I suspect very strongly that F # a major influence on the evolution of C # and. NET will have. F # has contributed to C # 2.0 Generics received. For C # 3.0 and LINQ other concepts in the functional world of object-oriented world were transmitted: type inference, lambda expressions and the very esoteric concept of the monad theory. I speculate that C # 5.0, C # 4.0 features when received from the dynamic world, again adapting concepts from the functional world. My wish for C # 5.0 features are: pattern matching, enhanced type inference, and metaprogramming.
I think you can say the following striking of F # (including other functional languages):
With F #, there are generics. With F #, there are lambda expressions. With F #, there is LINQ.
Thank F #!
view
I have to write a few basic blog entries F #. In the next blog entry will be about why you should actually use F #.
