Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations The Future of F#: Type Providers

The Future of F#: Type Providers



Joe Pamer presents what Type Providers coming in F# 3.0 are: a mechanism for accessing a multitude of external data source.


Joe Pamer is the Lead Developer for the F# team at Microsoft. He has been at Microsoft for six years, with much of that time having been spent on F#.

About the conference

Strange Loop is a multi-disciplinary conference that aims to bring together the developers and thinkers building tomorrow's technology in fields such as emerging languages, alternative databases, concurrency, distributed systems, mobile development, and the web.

Recorded at:

Jan 26, 2012

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Strange Loop

    by Alex Miller,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    If you're interested in other upcoming videos from Strange Loop, the full release schedule is here and all slides are here. If you want to be notified about Strange Loop announcements in the future, sign up for the mailing list.

  • sad truth

    by Alexandre Trépanier,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    the real problem with f# is the fact that you didnt follow anything of the c# syntax at all.. you sould have taken the scala route on that case..

    even now.. your LINQ is not exactly the same as C# LINQ..
    the way you represent methods is STUPIDLY unreable

    it should always be add (x,y -> z) not add x -> y -> z .. this is UNREADABLE and CLEARLY STUPID NERD CHOICE when your method return another method and have a method as parameter.. you can see how unreable this begin to be.. so all your doc is shit just because of this.. even the way we code should make sure we understand what is a parameter, what is a methodname, what is a return value... EASILY SEE.. you FAIL there and it's the main reason nobody is interested...

    now wtf.. with the NEW QUERY keyword... it's verbose as HELL .. you cant even think about a way to remove it like in c# or having just interogation point with open bracket or whatever.. anything else than having to type query ...

    and what with the "let mutable variable" why not "letm"..

    the only thing we wanted is a clean functional language with the most similarity possible to c# for the .net platform.. now scala as done it but it doesnt work on .net...

    seriously sad.. you should make a new language called A# and clean that shit up to the max so it become the best languages ever but as near as possible to c#.. (like when it doesn't matter you copy the c# syntax). f# cannot be that for so many reason and your still adding options (like linq) to it .. when they should be first class in the language.. (like scala)..

  • Re: sad truth

    by Alexandre Trépanier,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    oh and you "fun" keyword for delegate and function is also very verbose.. and your pipe operator and your assignment operator could be one caracter instead of two.. why not just "<" ">" it's not like we use those a lot(logical compare) anyway.. I would prefer "<<" ">>" when doing comparing and < and > when piping.. assignment is some kind of piping anyway so "<" would be perfect

    f# is full of bad design choice.. made by nerds for nerds.. but we are in 2014.. kinda very sad.. everytime i try to like it because of it's concice readable code.. i finally hate it for all those reasons.. Maybe i'm a scala guy at heart..


Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p