tethis

If you look at those benchmarks, for the same db queries on the same db backend, throughput and latency can differ by an order of magnitude. We're talking the difference between 200 or 2000 requests per second, or 50ms vs 500ms latency. That's not a rounding error.

But to succeed as a currency, it needs to encourage people to spend.

I am indeed referring to for-comprehensions. Any time you have nested flatMap/maps you can replace it with a for, since that's all a for-comprehension really is...

  computation1.flatMap { result1 =>
    computation2.flatMap { result2 =>
      computation3.map { result3 =>
        result2 + result3
      }
    }
  }

Becomes...

  val foobar = for {
    result1 <- computation1
    result2 <- computation2(result1)
    result3 <- computation3(result2)
  } yield {
    result2 + result3
  }

Or, since I'm using the async Postgres module which returns Futures, to make them run in parallel you need to create the futures beforehand. I often have something like this...

  val fProject = Project.findById(projectId)
  val fTask = Task.findById(taskId)

  for {
    projectOption <- fProject

    taskOption <- fTask

    students <- projectOption match {
      case Some(project) => Student.findByProject(projectId)
      case None => Future.successful(IndexedSeq[Student]())
    }

    result <- (projectOption, taskOption) match {
      case (Some(project), Some(task)) => { 
        /* do something with project, task and students */ 
      }
      case (None, _) => Future.successful(NotFound(s"Project $projectId not found"))
      case (_, None) => Future.successful(NotFound(s"Task $taskId not found"))
    }
  }
  yield result

By creating the futures first, they both run in parallel and their results are 'collected' by the for comprehension. In the first example, the computations necessarily run in sequence.

I'm using Play framework, for me, these for comprehensions are usually found in my controllers and the final result is an HTTP result.

Passing along failure can still be tricky but I find this much more organized than nesting callbacks.

But if the currency is deflationary with a coin limit, over the long term the only way more people can enter the market / make use the currency is for, as an example, $1 USD to be represented by smaller and smaller subdivisions of BTC. This necessarily increases the value of 1 BTC.

Why is there ever any incentive to do anything with BTC besides hoarding?

The point of these benchmarks is that, given the same database and the same queries, languages have different performance profiles.

If I build an application in Java and Python, with the same database backend, running the exact same set of SQL queries, the Java application should perform better.

The address bar works as both now, it seems that the search bar is left there so that it doesn't startle all the neophobes even more.

And it's important to note with Scala, a big part of its complexity comes from the practical philosophy of its creators: purity is sacrificed in order to actually make it work on the JVM the way we want it to.

I used to work with Java on the server-side, but I'm programming almost entirely in Scala now (I'm at a small shop where I was lucky enough to convince the boss to let me give it a go on a project last year) and I've got to say that it's completely changed the way I think about and solve problems. I learned Haskell in university and I'm trying to learn more, but I don't see it ever being accepted in our office.

The Scala syntax does (especially when working with async programming / Futures) suffer from problems, like the nested callback problem that Javascript also has, but there is an elegant solution in the language... you just have to know how to use it. But on the other hand, it doesn't look like a completely foreign language to Java developers and it's not too hard to get our new hires productive with it.

Providing additional information about the author is a logical fallacy now?

Also, see: http://www.logicalfallacies.info/relevance/fallacists/

And it would also only be for a specific user, rather than the dragnet surveillance (biggest fishing trip in history) that the NSA, et al, are conducting.

Are they preventing you from installing GNOME2 on your desktop?

Yeah, right, they "got hacked".

CKEditor 4 also supports inline editing like this.

Sweet jesus I cannot read that font.

It's also included by default in Play Framework.

I used it for a while, on a large project, and eventually came to hate it. I try to write as clean code as ppossible but still found the resulting mess of words, commas and arrows floating around at differing indentation levels to be much harder to read.

To me, even though javascripts syntax can be annoying, it's parentheses provide a certain amount of structure to the code.

Ooh, is there a story behind this one?

I've been pleasantly surprised using SBT... it's been doing the job for me for a year now and I haven't had any problems.

I know I like to talk about Haskell, even if it's too dense for me to grasp at a level where I could put it into production without jumping off a bridge.

This isn't really a "confession"... just someone gushing over a programming language in a terrible looking font.

Not if you have to type that out every single time...

Google Trends predicts own demise?

There certainly are ORMs available with Play!

I'm using one called Activate (http://activate-framework.org/) in a few of my latest projects and it's really simplified things. There's also Squeryl, ReactiveMongo, Slick...

We just had a ruling a couple months ago, up here in Canada, that a 3-year mandatory minimum sentence involve possession of a loaded firearm was unconstitutional as it is considered "cruel and unusual punishment".

Is such a challenge possible in the USA?

Let me know when you find that grave, because I'll join you after eating a huge bowl of chilli.

My thoughts exactly!