Our 8 years journey with Scala
summary
Eight years of adopting Scala lead to concrete outcomes: existing Java libraries stay reusable, bugs drop and the team reports 50% code reduction on trials; a real conversion project targets and achieves a rewrite of a legacy web app converted legacy Java app in 6 months with 5 people using Scala 2.9, Play 3.0 and a typesafe query library (plus a homegrown code generator), the team authors a 300-topic Japanese Scala book and releases GitBucket — 6,600 stars on GitHub.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:49Why did we need Scala?
- 2:49Strong interest in Scala
- 3:49We made a debut
- 6:30As a solution
- 7:31Project Brief
- 9:00Stumbling
- 9:56Slightly frowning
- 10:14Benefits
- 10:51Dissemination activities of Scala
- 13:01Issues have come to the fore again
- 14:06Daily Scala meetup
- 14:43Scala books reading club
- 15:07As it turns out
- 17:13The Scala situation in Japan
- 17:59ScalaMatsuri 2018
- 18:25Going forward
related talks
39mSix Years of Scala and Counting
48mBuying into Scala from the Inside and Out
38mMy first year in Scala
38mA song of types and errors (...)
22mAdopting Scala: The Next Steps
42mBuilding a Company on Scala
51mDeus Ex Scala: Finding a Home for Scala in the Corporate Machine
33mFrom Managing Scala to Managing People