Typesafe Changes Name to Lightbend

| by Matt Raible Follow 4 Followers on Mar 10, 2016. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

The company formerly known as Typesafe, inventors of the Scala programming language, has completed their renaming and is now known as Lightbend. Typesafe announced their plans to rename last May, stating at that time that it was expected to be a two month process. They invited community members to participate, and provided blog updates about their progress.

The reason for the renaming was two-fold. Firstly, they were seeking a change in strategy, and secondly they felt the name Typesafe, a name that had become synonymous with Scala, was misleading. While Scala was at their core, they found that they were developing a reputation beyond Scala. They also found that the majority of their customers were using Java and other JVM languages other than Scala.

Mark Brewer, CEO of Lightbend, said in a blog post that the company is challenged to accelerate the adoption of its Reactive Platform, based on Play, Akka and Spark. They’ve started this process by publishing the Reactive Manifesto and leading the Reactive Streams specification (to be included in JDK 9).

Brewer also named Lagom microservices framework as their latest product to help developers adopt reactive architectures, (available on GitHub). Earlier this month InfoQ published an interview with Jonas Bonér, CTO of Lightbend, where he discussed Lagom.

Community reaction to the name change was somewhat reserved. Commentors on Brewer’s blog post (and Hacker News) felt that the company was moving away from Scala and towards Enterprise Java. Brewer followed up with a blog post answering questions on the name change, saying they remain fully committed to the Scala language. He also mentioned Logam would publish its Java API first, since it’s been challenging to convert the expressive Scala APIs in their products to Java.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you