Community for F#

Blog articles of Community for F#

0
comment
on 9/15/2015 3:26 PM
The core of many web sites and web APIs is very simple. Given an HTTP request, produce a HTTP response. In F#, we can represent this as a function with type Request -> Response. To make our server scalable, we should make the function asynchronous to avoid unnecessary blocking of threads. In F#, this can be captured as Request -> Async<Response>. Sounds pretty simple, right? So why are there so many evil frameworks that make simple web programming difficult? Fortunately, there is a nice F# library called [...]
>> Read the full article
.
0
comment
on 9/15/2015 3:26 PM
The core of many web sites and web APIs is very simple. Given an HTTP request, produce a HTTP response. In F#, we can represent this as a function with type Request -> Response. To make our server scalable, we should make the function asynchronous to avoid unnecessary blocking of threads. In F#, this can be captured as Request -> Async<Response>. Sounds pretty simple, right? So why are there so many evil frameworks that make simple web programming difficult? Fortunately, there is a nice F# library cal[...]
>> Read the full article
.
0
comment
on 9/10/2015 12:00 AM
Tweet NOTE : read the rest of the series, or check out the source code. If you enjoy reading these exercises then please buy Crista’s book to support her work. Following on from the last post, we will look at the Go Forth style today.   Style 2 – Go Forth This style is named
>> Read the full article
.
0
comment
on 9/9/2015 9:14 AM
Most programming languages were designed before the age of web. This matters because the web changes many assumptions that typed functional language designers tak for granted. For example, programs do not run in a closed world, but must instead interact with (changing and likely unreliable) services and data sources, communication is often asynchronous or event-driven, and programs need to interoperate with untyped environments like JavaScript libraries. How can statically-typed programming languages [...]
>> Read the full article
.
0
comment
on 9/9/2015 9:14 AM
Most programming languages were designed before the age of web. This matters because the web changes many assumptions that typed functional language designers tak for granted. For example, programs do not run in a closed world, but must instead interact with (changing and likely unreliable) services and data sources, communication is often asynchronous or event-driven, and programs need to interoperate with untyped environments like JavaScript libraries. How can statically-typed programming languages adapt[...]
>> Read the full article
.
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper