This presentation will describe an approach to doing this building on nothing more than Scala and Akka and demonstrate the approach abstracted away from the tedium of the backing implementation, of which several will be demonstrated.

In this session he walks through building a simple website using Elnode and talks about the emerging world of EmacsLisp build and development tools as well as recent developments in EmacsLisp like lexical scope and actor like asynchrony.

LexiFi has created an embedded domain-specific language to describe financial contracts. This symbolic description streamlines the processing chain for such contracts and greatly improves the time-to-market to support new kinds of contracts in our applications and those of our technology partners. LexiFi has built its technology on top of OCaml for more than ten years and this wonderful language has become so important to us that we are contributing more and more on improving OCaml itself.

Learn how to cater to full-scale data visualization, exploratory interactive development and advanced customizations too.

Static type systems are the world’s most widely applied formal method, in daily use by millions of programmers.

The trouble is that weak type systems give types a bad name; they get in your way and stop you from writing the programs you want to write. And that leads to the familiar but fruitless static-vs-dynamic debate which I hope to avoid entirely.

This includes:

• Using Scala 2.10's macro features to compile certain Scala code including form validation and actors into JavaScript the executes the same logic across the address spaces
• Supporting asynchronous Actor messaging seamlessly across the HTTP connection and across address spaces
• Detection of page building with Futures and Streams and automatically pushing those changes to the browser... doing page rendering across time
• Simplified support for use of Futures and Streams in REST responses going across time
• Enhancements to Lift's designer friendly templating system that gives the HTML side of the house more power
• Automatic class reloading so that change to code get picked up on page reload without a restart... saving time.

In some ways they are very different creatures: Scala uses strong types, has come from an academic background and is influenced by ML and Haskell; Clojure is a straight-forward port of LISP with Java compatibility added, it has come from a pragmatic background of real-world problems.

Adherents of both languages tend to be unable to get past the fundamental difference in approach regarding typing, checking and compilation. However both share some fundamental aspects: both represent a distillation of understanding from working with object-orientated code, both rely on first-order functions and functional paradigms to deliver their most distinctive advantages, both aim to leverage an ecosystem to bring functional programming to the mass audience it has consistently failed to do hitherto.

As someone who has and does work with both languages I want to try and point what the real differences are between the two, what they have to learn from one another and speculate about what the future might look like in the world of "Enterprise".

F# now includes contributions that range from Cloud IDE platforms, Cloud Compute frameworks, Data interoperability components, Cross-platform execution, Try F#, MonoDevelop, and even Emacs editor integration with surprising tooling support, as well as the Visual F# tools from Microsoft and the broader NuGet package ecosystem. Don will also talk about some of the latest contributions from Microsoft Research, including new type provider components for F#, and describe how his team work with the Visual F# team and other teams around Microsoft. There will also be demos of some fun new stuff that’s been going on with F# at MSR and the community.

We will also look at how to bring functional reactive code to your data instead of bringing the data to the code as most stream processing systems work.