We are committed to Scala
Support for Scala and the Play and Spray framework is by far the most requested feature of DripStat.
We have promised support for this to our users in the past. So it is no suprise that we got a ton of angry mails after yesterday’s release contained even more Java async features and not Scala support. I guess its time to answer a few questions:
Why have you of late been focusing on Java Async support and not implementing Scala support?
Scala’s frameworks are completely asynchronous from top to bottom. We saw other vendors who added Scala support and it was terrible and useless cause the APM wasn’t designed to track asynchronous calls in the first place.
Seeing the growth of Scala and reactive programming we knew we had to bake it async support in our agent from the ground up. To do this, we decided the best way would be to work with stuff we already know, so we decided to make the implementation for Java’s asynchronous libraries first. This helped us learn about the various problems in supporting async and form the right set of abstractions in the agent, on our backend and in the UI to support it.
Why did yesterday’s release focus again on Java async and not Scala?
Our initial release of the agent only partially supported most of the async libraries in the Java world, but with yesterday’s release we have covered the ground for the most popular java async libs and made sure our agent is robust with async support.
When is Scala support coming?
We are entirely focused on Scala at the moment. As I write this blog post, we are working tirelessly only with Scala code to add support for Play and Spray frameworks. Our experience adding support for Async in java should help us achieve this very swiftly.
Next week we should have some announcements that will make the Scala people happy!