scala in-practice-3-years by patric fornasier, springr, presented at pune scala symposium 2014,...
DESCRIPTION
3 years ago, Springer decided to use Scala on a large, strategic project. This talk is about the journey the development teams made. Why did they choose Scala in the first place? Did they get what they hoped for? What challenges and surprises did they encounter along the way? And, most importantly, are they still happy with their choice?TRANSCRIPT
![Page 2: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/2.jpg)
Context
![Page 3: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/3.jpg)
Context
Pat
Springer
Software
Engineer
Technical
Principal
10+ years
Academic
Publisher
Pretty Large
Springer
Link
Strategic
95 % Online
Revenue66 % Total
Revenue
9 Mio items
2TB XML
Re-built
3 years ago
Content
Delivery
Platform
52 Mio
PageViews / Month
99.9%
Availability
Scala NoSql
Co-Sourced
Team
TW
Ex-TW
SpringerGlobal
CD
![Page 4: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/4.jpg)
SpringerLink
![Page 5: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/5.jpg)
Timeline
Startdevelopment
CyclingTrip
Re-joined
Product -> platformPaying back tech debt
Today
04/11 04/12 08/13 04/14
Inception
05/12 09/12
BookfairRelease
RDLive
User migration,enhancements
LinkLive
SmartBooksLive
Enhancements
![Page 6: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/6.jpg)
Looking back: why scala?• Increase productivity
• Be more attractive employer
• Team decision
![Page 7: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/7.jpg)
Looking back: good vs badGood
• Functional programming
• Terse syntax
• JVM ecosystem
• Gentle learning curve
• DSL friendly syntax
• Motivated team
Bad
• Tool support
• Compilation times
• Language complexity #moreRope
![Page 8: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/8.jpg)
Fast-forward
![Page 9: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/9.jpg)
Fast-forward (Aug 2013)
• 2.5 years into project
• 1.5 years of weekly live releases
• 100k LOC
• >10k commits
• >90 committers
![Page 10: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/10.jpg)
Fast-forward (Aug 2013)
• 2.5 years into project
• 1.5 years of weekly live releases
• 100k LOC
• >10k commits
• >90 committers
not all related to Scala - to be fair
• Poor feedback loops
• Lots of accidental complexity
![Page 11: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/11.jpg)
Trend (2 years)
LOC
~ 100k
![Page 12: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/12.jpg)
Trend (2 years)
build time
LOC
![Page 13: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/13.jpg)
Trend (2 years)
build time
LOC• 1:34 min src/main
• 6:44 min src/test
• 8:18 min total
![Page 14: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/14.jpg)
What did we do?
![Page 15: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/15.jpg)
What did we do• Reduced build time
• Improved feedback loops
• Reduced accidental complexity
![Page 16: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/16.jpg)
Build time• Reduced size of codebase (broke off vertical slices, pulled out APIs, pulled out libraries,
removed unused features, removed low-value tests, etc.)
• Reduced usage of certain language features (esp. traits and implicits)
![Page 17: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/17.jpg)
Trend (Dec 2013)
LOC
![Page 18: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/18.jpg)
Trend (Dec 2013)
build time
# traits
LOC
unable to compile on 13” macbook
![Page 19: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/19.jpg)
Trend (Dec 2013)
build time
# traits
LOC
unable to compile on 13” macbook
![Page 20: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/20.jpg)
The problem with traits• Will re-compile on every class the trait is mixed in
• Slows down dev-build cycle
• Will result in byte code bloat
• Will compile *a lot* slower
!
For faster compile times:
• Use pure traits
• Use old-school composition for code re-use
• Use pure functions via imports (e.g. import Foo._)
• If unavoidable, use inheritance for code re-use
![Page 21: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/21.jpg)
Build time
![Page 22: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/22.jpg)
Build time
• 1:34 min src/main
• 6:44 min src/test
• 8:18 min total
![Page 23: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/23.jpg)
Build time
• 1:34 min src/main
• 6:44 min src/test
• 8:18 min total
• 0:24 min src/main
• 3:11 min src/test
• 3:35 min total
![Page 24: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/24.jpg)
Build time (on CI server)
• Incremental compilation on CI
• Only one dedicated CI agent
• Physical build servers
• CPUs with higher clock speed
![Page 25: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/25.jpg)
Build time (on CI server)
• Incremental compilation on CI
• Only one dedicated CI agent
• Physical build servers
• CPUs with higher clock speed
![Page 26: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/26.jpg)
Complexity
![Page 27: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/27.jpg)
Complexity• There’s still a lot of code in our codebase that is hard to read
• It seems to be very easy to shoot yourself in the foot with Scala
• Scala *is* complex (and that’s why scalac will never be as fast as javac)
![Page 28: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/28.jpg)
Complexity• There’s still a lot of code in our codebase that is hard to read
• It seems to be very easy to shoot yourself in the foot with Scala
• Scala *is* complex (and that’s why scalac will never be as fast as javac)
Invariant/covariant/contravariant types (T, +T and -T)Refined types (new Foo {...})Structural types (x: {def y: Int})Path dependant types (a.B)Specialized types (@specialized)Self types (this =>)Projection types (A#B)Existential types (M[_])
Type bounds (<:, >:) Type constraints (=:=, <:< and <%<)
Type members (type T)Type aliases (type T = Int)
Type classes ( (implicit ...) )View bounds (<%)
Higher kinded types (* => *)F-Bounded type polymorphism (M[T <: M[T]])
http://nurkiewicz.github.io/talks/2014/scalar/#/16
![Page 29: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/29.jpg)
Not opinionated
For example: http://twitter.github.io/effectivescala/
• Many ways to do the same thing
• Coding conventions help, but only so much
![Page 30: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/30.jpg)
Not opinionated
def foo() = "foo"def bar = "bar"!foofoo()barbar() // won't compile
For example: http://twitter.github.io/effectivescala/
• Many ways to do the same thing
• Coding conventions help, but only so much
![Page 31: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/31.jpg)
Not opinionated
def foo() = "foo"def bar = "bar"!foofoo()barbar() // won't compile
For example: http://twitter.github.io/effectivescala/
• Many ways to do the same thing
• Coding conventions help, but only so much
def baz(x: String) = x“x”.charAt(0)“x” charAt(0) // won't compile“x”.charAt 0 // won't compile“x” charAt 0baz("x")baz “x" // won't compile
![Page 32: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/32.jpg)
Not opinionated
def foo() = "foo"def bar = "bar"!foofoo()barbar() // won't compile
list.foreach { x => println(x) }list.foreach ( x => println(x) )list.foreach { println(_) }list.foreach ( println(_) )list foreach { x => println(x) }list foreach ( x => println(x) )list foreach { println(_) }list foreach ( println(_) )
For example: http://twitter.github.io/effectivescala/
• Many ways to do the same thing
• Coding conventions help, but only so much
def baz(x: String) = x“x”.charAt(0)“x” charAt(0) // won't compile“x”.charAt 0 // won't compile“x” charAt 0baz("x")baz “x" // won't compile
![Page 33: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/33.jpg)
Not opinionated
def foo() = "foo"def bar = "bar"!foofoo()barbar() // won't compile
list.foreach { x => println(x) }list.foreach ( x => println(x) )list.foreach { println(_) }list.foreach ( println(_) )list foreach { x => println(x) }list foreach ( x => println(x) )list foreach { println(_) }list foreach ( println(_) )
if (foo) "x" else "y" foo match { case true => "x" case _ => "y"}
For example: http://twitter.github.io/effectivescala/
• Many ways to do the same thing
• Coding conventions help, but only so much
def baz(x: String) = x“x”.charAt(0)“x” charAt(0) // won't compile“x”.charAt 0 // won't compile“x” charAt 0baz("x")baz “x" // won't compile
![Page 35: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/35.jpg)
SurprisesList(1, 2, 3).toSet
http://dan.bodar.com/2013/12/04/wat-scala/
![Page 36: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/36.jpg)
SurprisesList(1, 2, 3).toSet scala.collection.immutable.Set[Int] = Set(1, 2, 3)
http://dan.bodar.com/2013/12/04/wat-scala/
![Page 37: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/37.jpg)
SurprisesList(1, 2, 3).toSet scala.collection.immutable.Set[Int] = Set(1, 2, 3)
List(1, 2, 3).toSet()
http://dan.bodar.com/2013/12/04/wat-scala/
![Page 38: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/38.jpg)
SurprisesList(1, 2, 3).toSet scala.collection.immutable.Set[Int] = Set(1, 2, 3)
List(1, 2, 3).toSet()Boolean = false
http://dan.bodar.com/2013/12/04/wat-scala/
![Page 39: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/39.jpg)
Implicits• Can make it very hard to read code
• Tool support is very bad
• Impacts compilation time
• Surprising behaviour (esp. when used with overloaded methods or optional params)
![Page 40: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/40.jpg)
Tooling
def handle(response: HttpResponse, request: HttpRequest)
• Tool support is still very basic
• Makes it hard to continuously refactor (which means people are less likely to do it)
![Page 41: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/41.jpg)
Tooling
def handle(response: HttpResponse, request: HttpRequest)
• Tool support is still very basic
• Makes it hard to continuously refactor (which means people are less likely to do it)
no luck with “change signature” refactoring support
![Page 42: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/42.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
![Page 43: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/43.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
![Page 44: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/44.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
trait B extends A { override def foo = "b"}
![Page 45: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/45.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
trait B extends A { override def foo = "b"}
class C extends A with Bnew C().foo
![Page 46: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/46.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
trait B extends A { override def foo = "b"}
class C extends A with Bnew C().foo
"b"
![Page 47: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/47.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
trait B extends A { override def foo = "b"}
class C extends A with Bnew C().foo
"b"
class D extends B with Anew D().foo
![Page 48: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/48.jpg)
Trait entanglements• Makes it difficult to reason about behaviour
trait A { def foo = "a"}
trait B extends A { override def foo = "b"}
class C extends A with Bnew C().foo
"b"
class D extends B with Anew D().foo
"b"
![Page 49: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/49.jpg)
Trait entanglements (2)
ArticlePageSteps
WebDriverSupport
AuthorStepsCoverImageSteps
SummarySection
Waiter SectionPageSteps
CommonPageSteps
WebElementSupport
Assertions
Uris TripleEquals
OnHost TripleEqualsSupport
MachineNames
![Page 50: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/50.jpg)
Trait entanglements (3)
ArticlePageSteps_0
WebDriverSupport_1 AuthorSteps_1 CoverImageSteps_1 SummarySection_1Waiter_1 SectionPageSteps_1 CommonPageSteps_1
CommonPageSteps_2 WebElementSupport_2Assertions_2 WebDriverSupport_2Uris_2
WebElementSupport_3 WebDriverSupport_3Uris_3 TripleEquals_3 OnHost_3
OnHost_4 TripleEqualsSupport_4 MachineNames_4
MachineNames_5
![Page 51: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/51.jpg)
Trait entanglements (3)
ArticlePageSteps_0
WebDriverSupport_1 AuthorSteps_1 CoverImageSteps_1 SummarySection_1Waiter_1 SectionPageSteps_1 CommonPageSteps_1
CommonPageSteps_2 WebElementSupport_2Assertions_2 WebDriverSupport_2Uris_2
WebElementSupport_3 WebDriverSupport_3Uris_3 TripleEquals_3 OnHost_3
OnHost_4 TripleEqualsSupport_4 MachineNames_4
MachineNames_5
![Page 52: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/52.jpg)
Trait entanglements (4)
ArticlePageTests_0
ArticlePageSteps_1 AboutSectionSteps_1 SearchResultsPageSteps_1 Uris_1 ArticleTestFixture_1 JavascriptSupport_1 IssuePageSteps_1 CommonAbstractSteps_1 GoogleAnalyticsSteps_1 FakeEntitlementSteps_1 ExportCitationPageSteps_1 FullTextPageSteps_1 OtherActionsSectionSteps_1
WebDriverSupport_2 AuthorSteps_2 CoverImageSteps_2 SummarySection_2Waiter_2 SectionPageSteps_2 CommonPageSteps_2
CommonPageSteps_3 WebElementSupport_3Assertions_3 WebDriverSupport_3Uris_3
WebElementSupport_4 WebDriverSupport_4Uris_4 TripleEquals_4 OnHost_4
OnHost_5 TripleEqualsSupport_5 MachineNames_5
MachineNames_6
![Page 53: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/53.jpg)
Trait entanglements (4)
ArticlePageTests_0
ArticlePageSteps_1 AboutSectionSteps_1 SearchResultsPageSteps_1 Uris_1 ArticleTestFixture_1 JavascriptSupport_1 IssuePageSteps_1 CommonAbstractSteps_1 GoogleAnalyticsSteps_1 FakeEntitlementSteps_1 ExportCitationPageSteps_1 FullTextPageSteps_1 OtherActionsSectionSteps_1
WebDriverSupport_2 AuthorSteps_2 CoverImageSteps_2 SummarySection_2Waiter_2 SectionPageSteps_2 CommonPageSteps_2
CommonPageSteps_3 WebElementSupport_3Assertions_3 WebDriverSupport_3Uris_3
WebElementSupport_4 WebDriverSupport_4Uris_4 TripleEquals_4 OnHost_4
OnHost_5 TripleEqualsSupport_5 MachineNames_5
MachineNames_6
Imagine many more circle here
![Page 54: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/54.jpg)
So, what’s next?
![Page 55: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/55.jpg)
Today• We’ve delivered successfully using Scala
• Don’t think we’re more productive (pure gut feeling, though)
• We try to stick to the good parts (conventions, functional programming, pattern matching, etc.)
• Complexity, slow compilation and lack of tool support are real problems
![Page 56: Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Scala Symposium 2014, ThoughtWorks](https://reader031.vdocuments.site/reader031/viewer/2022020217/547ec412b4af9faa158b570b/html5/thumbnails/56.jpg)
The future• No urgency to move away from Scala or re-write existing systems
• Java 8 is an alternative
• Smaller teams and apps will probably lead to more polyglotism (and less Scala)