Your data is showing that Scala grew from 0.01% to 0.03% over the past two years. Sounds impressive, right?

It's a relative number. Whenever somebody quotes growth numbers instead of absolute numbers, they are trying to hide something.

Let's take a look at the absolute numbers:

http://www.indeed.com/jobtrends?q=scala%2C+java&l=

As you can see, Scala's line is a flatline around 0 compared to Java.

There is very little evidence of that. Do a search for Scala, Clojure or Haskell on the main indicator web sites (job boards, StackOverflow, TIOBE, indeed.com, etc...) and you'll find they are as insignificant today as they were five years ago compared to the mainstream languages.

I'm puzzled why you think this is good news for Haskell. The lead developer and architect of GHC and authority in parallel Haskell is announcing that he's taking a position that won't allow him to spend much time working on GHC, and he might even stop using Haskell completely.

It's great news for Simon but terrible news for Haskell.

Anybody encounter this problem? It's very annoying.

And a good reminder why I don't let third party access my Gmail inbox :-(

The article is about Apple's stock price, and I'm not sure you understand how that part works.

Yes, Apple will continue to make billions of dollars every quarter for quite a while, but their stock is likely to drop down significantly in the coming year.

The reason why you see big .js files is that it's not easy to split your code in a.js and have it include b.js from the server.

So, exactly like exceptions.

That's a bit harsh. JetBrains and the developers of the compiler are certainly aware of the Maybe/Option approach, they chose not to use it. Their approach is not as composable as Haskell's but much more practical and more readable in my opinion.

If anything, the fact that Option is still used so rarely in Scala is an indication that maybe, that experiment has failed.

In this case, wouldn't it have been better to ship 1.0 with generics?

Retrofitting generics in a language already released with an existing code base sure doesn't seem like the best way to make sure the feature is "done right".

It always takes longer to write short emails, which is why so few people do it.

Their potential customers are not people standing in line for hours to buy an iPhone, so the ad is spot on.

You sound exactly like these people standing in line for iPhones in the Samsung commercial.

What high price points? iOS devices (phones and tablets) are pretty much at the same price as the competition.

If we standardize on one operating system, I definitely prefer a future where we have thousands of phones to choose from and not just five.

Thank you Google for saving us from an Apple monopoly.