3 ms·
> Typesafe->Lightbend transition The renaming never affected the staffing of the Scala team at Lightbend -- we've been doing about 2/3 of core Scala developmen
by adriaanm 9y ago
> Typesafe->Lightbend transition
The renaming never affected the staffing of the Scala team at Lightbend -- we've been doing about 2/3 of core Scala development (major thank you to the community for the other third!) since 2.10 (when I went from post-doc in Martin's lab to the Scala team lead position).
In my opinion, it was a good thing that feature development slowed down in Scala 2.x (while Martin pushed the research frontier forward in Dotty), so we could focus on (in no particular order) compiler performance, a new back-end and optimizer, Java 8 support, modularization,...
- atemerev 9y agoYes, it all went in a good way. However, this was a scary time, observing Typesafe (now Lightbend) slowly transforming into a garden variety enterprise Java consulting shop, and watching more and more core platforms like Akka being adapted back to Java... Things look better now. :)
- adriaanm 9y agoGood to hear! I agree :-) It was a necessary transition because we need to keep attracting customers that initially are reluctant to invest in Scala training. We've found our Java APIs to be a potent gateway drug to Scala, with many of our customers who begin with the Java APIs quickly realizing they'll be even more productive with Scala :-)
- AheadOfTime295 9y agoFacilitating contributions from the Scala community, what can be improved: [0] https://github.com/scala/scala/pull/5515 https://github.com/scala/scala/pull/5515 [1] https://failex.blogspot.nl/2017/04/why-i-didnt-sign-scala-cla.html https://failex.blogspot.nl/2017/04/why-i-didnt-sign-scala-cl...