<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: scala</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/scala.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2013-07-31T10:15:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>How do I choose between asynchronous web frameworks? My tech group is fairly language agnostic and we're trying to standardize on some technologies.</title><link href="https://simonwillison.net/2013/Jul/31/how-do-i-choose/#atom-tag" rel="alternate"/><published>2013-07-31T10:15:00+00:00</published><updated>2013-07-31T10:15:00+00:00</updated><id>https://simonwillison.net/2013/Jul/31/how-do-i-choose/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/How-do-I-choose-between-asynchronous-web-frameworks-My-tech-group-is-fairly-language-agnostic-and-were-trying-to-standardize-on-some-technologies/answer/Simon-Willison"&gt;How do I choose between asynchronous web frameworks? My tech group is fairly language agnostic and we&amp;#39;re trying to standardize on some technologies.&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Since they are all pretty close to each other and it sounds like your tech group's skills would support any of them, I would suggest having your tram build a simple prototype in all three so you can compare them for your own particular team and situation.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/frameworks"&gt;frameworks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nodejs"&gt;nodejs&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/play"&gt;play&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tornado"&gt;tornado&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webapps"&gt;webapps&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="frameworks"/><category term="javascript"/><category term="nodejs"/><category term="play"/><category term="python"/><category term="scala"/><category term="tornado"/><category term="webapps"/><category term="quora"/></entry><entry><title>Can Scala gain wider usage than Java any time soon?</title><link href="https://simonwillison.net/2012/Feb/11/can-scala-gain-wider/#atom-tag" rel="alternate"/><published>2012-02-11T17:17:00+00:00</published><updated>2012-02-11T17:17:00+00:00</updated><id>https://simonwillison.net/2012/Feb/11/can-scala-gain-wider/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Can-Scala-gain-wider-usage-than-Java-any-time-soon/answer/Simon-Willison"&gt;Can Scala gain wider usage than Java any time soon?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;No, because Scala is harder to master than Java.&lt;/p&gt;

&lt;p&gt;(By "master" I mean get to the point where you can read and understand code written by someone else, no matter what language features and idioms they are using)&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/concurrency"&gt;concurrency&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/programming"&gt;programming&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-development"&gt;web-development&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="concurrency"/><category term="java"/><category term="programming"/><category term="scala"/><category term="scaling"/><category term="web-development"/><category term="quora"/></entry><entry><title>Where can I find great Java/Scala developers in London?</title><link href="https://simonwillison.net/2012/Jan/22/where-can-i-find/#atom-tag" rel="alternate"/><published>2012-01-22T10:36:00+00:00</published><updated>2012-01-22T10:36:00+00:00</updated><id>https://simonwillison.net/2012/Jan/22/where-can-i-find/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/Where-can-I-find-great-Java-Scala-developers-in-London/answer/Simon-Willison"&gt;Where can I find great Java/Scala developers in London?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;There are quite a few Scala events in London - here are the ones we know about at the moment: &lt;span&gt;&lt;a href="http://lanyrd.com/topics/scala/in/london/"&gt;http://lanyrd.com/topics/scala/i...&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;The Scala Days conference at the Barbican in April looks like a particularly good place to find Scala developers. Since it's still a relatively niche language I imagine there are a bunch of Java developers who would like the opportunity to work with it full time.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/london"&gt;london&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recruiting"&gt;recruiting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="java"/><category term="london"/><category term="recruiting"/><category term="scala"/><category term="quora"/></entry><entry><title>What's powering the Content API?</title><link href="https://simonwillison.net/2010/May/24/solr/#atom-tag" rel="alternate"/><published>2010-05-24T14:08:00+00:00</published><updated>2010-05-24T14:08:00+00:00</updated><id>https://simonwillison.net/2010/May/24/solr/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.guardian.co.uk/open-platform/blog/what-is-powering-the-content-api"&gt;What&amp;#x27;s powering the Content API?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The new Guardian Content API runs on Solr, scaled using EC2 and Solr replication and with a Scala web service layer sitting between Solr and the API’s end users.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apis"&gt;apis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/contentapi"&gt;contentapi&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ec2"&gt;ec2&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/guardian"&gt;guardian&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openplatform"&gt;openplatform&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/solr"&gt;solr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;&lt;/p&gt;



</summary><category term="apis"/><category term="contentapi"/><category term="ec2"/><category term="guardian"/><category term="openplatform"/><category term="scala"/><category term="scaling"/><category term="solr"/><category term="recovered"/></entry><entry><title>Using Scala with Google App Engine</title><link href="https://simonwillison.net/2009/Apr/11/print/#atom-tag" rel="alternate"/><published>2009-04-11T15:28:48+00:00</published><updated>2009-04-11T15:28:48+00:00</updated><id>https://simonwillison.net/2009/Apr/11/print/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.riffraff.info/2009/4/9/using-scala-with-google-app-engine"&gt;Using Scala with Google App Engine&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Scala works, but I haven’t seen confirmation on actors yet (which are likely to break due to their dependency on threads).


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-app-engine"&gt;google-app-engine&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/threads"&gt;threads&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="google-app-engine"/><category term="java"/><category term="scala"/><category term="threads"/></entry><entry><title>Kestrel</title><link href="https://simonwillison.net/2009/Feb/26/kestrel/#atom-tag" rel="alternate"/><published>2009-02-26T10:20:24+00:00</published><updated>2009-02-26T10:20:24+00:00</updated><id>https://simonwillison.net/2009/Feb/26/kestrel/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://robey.lag.net/2008/11/27/scarling-to-kestrel.html"&gt;Kestrel&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Twitter’s Robey Pointer rewrote their Starling message queue in 1500 lines of Scala, adding reliable fetch (where consumers can confirm their receipt of an item) and blocking fetches, which reduce the need for consumers to poll for updates (and hence solve my only beef with the original Starling). I haven’t tried running this on a low spec VPS yet but it looks very promising.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/kestrel"&gt;kestrel&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/message-queues"&gt;message-queues&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/robey-pointer"&gt;robey-pointer&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scala"&gt;scala&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/starling"&gt;starling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="kestrel"/><category term="message-queues"/><category term="robey-pointer"/><category term="scala"/><category term="starling"/><category term="twitter"/></entry></feed>