August 18, 2009
Functional Programming & Microsoft
Small presentation about "Why MS trying to adopt functional programming in their programming languages...
Subscribe to:
Post Comments (Atom)
About Me
- Alex Ott
- Primary interests - Unix Programming, Unixes (Solaris, Linux, *BSD), Content filtering. Physicist, as first education, also finished MBA at Magdeburg University. Home page is located at http://alexott.net/
Followers
Links to my resources
Labels
- 2010 (3)
- 2011 (1)
- acer (1)
- algorithms (1)
- article (14)
- asio (4)
- book (25)
- boost (20)
- c++ (34)
- cedet (11)
- clojure (19)
- cmake (1)
- common-lisp (3)
- content filtering (9)
- cs (1)
- cuda (1)
- data mining (1)
- DSL (1)
- eclipse (1)
- education (1)
- emacs (66)
- emulation (1)
- erlang (2)
- f# (5)
- file formats (11)
- fp (25)
- germany (1)
- git (4)
- google (3)
- gpu (1)
- hadoop (3)
- handheld (1)
- hardware (1)
- haskell (11)
- home (1)
- humor (1)
- incanter (1)
- information retrieval (1)
- instant messaging (1)
- internet (1)
- it (5)
- java (1)
- jenkins (1)
- job (3)
- latex (1)
- life (5)
- linux (3)
- lisp (1)
- lucene (1)
- mac (9)
- machine-learning (2)
- mahout (1)
- mapreduce (1)
- maven (1)
- microsoft (2)
- msoffice (10)
- muse (1)
- ocaml (1)
- opencl (1)
- opensolaris (1)
- opensource (1)
- oss (3)
- palm (1)
- personal (1)
- photography (2)
- presentations (1)
- programming (10)
- quality (1)
- R (1)
- ruby (1)
- russia (1)
- scala (1)
- scheme (5)
- security (1)
- sicp (1)
- software development (2)
- solaris (2)
- spirit (1)
- squid (1)
- testing (2)
- tika (1)
- tips (1)
- travel (1)
- unix (1)
- vacation (1)
- vcs (11)
- version control (1)
- video (1)
- windows (1)
- work (7)
2 comments:
So the main reason to choose F# over Haskell seems to be the .Net platform.
I suppose with Mono, you needn't even fret the vendor lock-in so much, right?
from the first point of view - yes, there is no vendor lock with mono. But F# uses .Net libraries, that not covered by free MS licenses
Post a Comment