Hello Fernando,
As always, it depends. If it's just for that issue, I wouldn't, yet. Btw, I've add my comment to that issue, with a workaround that can be applied with existing spray APIs.
Since akka-http (experimental) is part of akka, sources are in akka github repository, release-2.3-dev branch (see
https://github.com/akka/akka/tree/release-2.3-dev ). Besides binaries, source jars are published with releases and available on Maven Central repo - just look under
http://repo1.maven.org/maven2/com/typesafe/akka/ for all artifacts starting with akka-http.
So, if planning to release/go-live soon, before akka-http and akka-streams reaches general availability, I know I wouldn't go with akka-http yet.
Otherwise, if you can afford luxury and wait for GA, starting with akka-http should cut down the costs - with spray one will eventually have to migrate to akka-http. I guess akka team is eager to get more feedback and testing from community on akka-http APIs. You have opportunity to shape the APIs before they become generally available, later they would be harder to change - as Joshua Bloch phrased it "Public APIs are forever - one chance to get it right" (see
http://lcsd05.cs.tamu.edu/slides/keynote.pdf ). Be aware also, that akka modules labeled as experimental are not labeled like that just for fun. People got burnt in the past depending too much on experimental akka features/modules (see
https://groups.google.com/d/msg/akka-user/8fZ75MlVEYc/YaZGsysG8mcJ ). I personally doubt akka-streams and akka-http will have same destiny as akka io pipelines, still be cautious when making your decision.
Kind regards,
Stevo Slavic.