Concurrency. Functional. Singlepage. - Fwd: Re: [luny-talk] What I am up to

Skip to first unread message


Nov 3, 2013, 12:55:55 PM11/3/13
to BTG
---- Original message -----
From: Ajai Khattri <>
To: NY Metro are technical discussion and events <>
Subject: Re: [luny-talk] What I am up to
Date: Tue, 29 Oct 2013 01:08:25 -0400

On Mon, Oct 28, 2013 at 01:22:55PM -0400, Ron Guerin wrote:

> I get that no one tool is right for everything, but seriously people
> (you language developers, wherever you are), you're not even trying anymore.

The way I look at it is there are styles that become relevant and others
become less so (or ultimately irrelevant). Right know it seems three
are going on:

1) Concurrency demands are driving the design and implementation of
languages that support that (Scala, Go, etc).

2) Functional programming is becoming a viable option (Haskell, Erlang,
Clojure, etc).

3) The front-end is moving away from the traditional HTML + CSS +
JavaScript pages generated from server-side code, to mostly just
that updates the page (i.e. single-page apps). Hence the rise of things
like Ember, Backbone and AngularJS).

In some cases, the languages above might cover more than one style, e.g.
Scala addresses concurrency but can be used in a functional style too.

If you are a Java shop, you are more likely to be looking at things that
run on the JVM (Scala, Clojure).

If you're writing code for Google App Engine, or Heroku or some other
PaaS, you will only have a subset of languages to choose from anyway.

Ultimately, the language choice is more influenced by things like
infrastructure, availability of developers, culture, etc. and in that
sense we need to have several choices for each.

talk mailing list
List info and Guidelines:
Your subscribed address is:
Your options page is:

--- Join the BerkeleyTIP-Global mail list - All Freedom SW, HW & Culture.

Reply all
Reply to author
0 new messages