Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Scala Experience ReportMark Needham and Liz Douglass
Funny image?
Funny image?
Does it really speed                               up the development                               as was hoped?Should th...
TestingTemplating Domain
Testing
scalatest
Unit testing
Functional Testing
Test DSL
First class functions
Test DSL
# of unit tests:         449# of integration tests:         280# of functional tests:         353
Unit testing
Unit testing
Unit testing
Templating
Scalatra
Scalatra   Scalate
SSP                      scamlScalatra   Scalate                       jade                     Mustache
Controller
Mustache
Jade
View Helper
Jade
Domain
Presentation Model
XML
More XML
More XML
And not just XML…
Going too far!
TraitsWhich example was this supposed to be?ContentRepository - JUNE
Traits1. Utilitieshttp://blog.schauderhaft.de/2011/08/21/usage-patterns-of-scala-traits/
Traits2. Presentation Model
Traits3. Helpers to Helpers
Traits4. Wanna be objects
Traits5. Type container
Traits6. Traits with standards
Implicits
Implicits
Implicits
Options
Tendency to     have fewer        testsRefactoring                       Code                  discoverability
In Retrospect …
Does it really speed                               up the development                               as was hoped?Should th...
Scala compiler slower than    Java’s
Questions
Scala: An experience report
Scala: An experience report
Scala: An experience report
Upcoming SlideShare
Loading in …5
×

Scala: An experience report

3,988 views

Published on

An experience report after using scala for 6 months.

Published in: Technology
  • Be the first to comment

Scala: An experience report

  1. 1. Scala Experience ReportMark Needham and Liz Douglass
  2. 2. Funny image?
  3. 3. Funny image?
  4. 4. Does it really speed up the development as was hoped?Should the projecthave been done in Java? Is it easier to maintain and extend than an equivalent Java code What features of the base? language and patterns of usage have been successes?
  5. 5. TestingTemplating Domain
  6. 6. Testing
  7. 7. scalatest
  8. 8. Unit testing
  9. 9. Functional Testing
  10. 10. Test DSL
  11. 11. First class functions
  12. 12. Test DSL
  13. 13. # of unit tests: 449# of integration tests: 280# of functional tests: 353
  14. 14. Unit testing
  15. 15. Unit testing
  16. 16. Unit testing
  17. 17. Templating
  18. 18. Scalatra
  19. 19. Scalatra Scalate
  20. 20. SSP scamlScalatra Scalate jade Mustache
  21. 21. Controller
  22. 22. Mustache
  23. 23. Jade
  24. 24. View Helper
  25. 25. Jade
  26. 26. Domain
  27. 27. Presentation Model
  28. 28. XML
  29. 29. More XML
  30. 30. More XML
  31. 31. And not just XML…
  32. 32. Going too far!
  33. 33. TraitsWhich example was this supposed to be?ContentRepository - JUNE
  34. 34. Traits1. Utilitieshttp://blog.schauderhaft.de/2011/08/21/usage-patterns-of-scala-traits/
  35. 35. Traits2. Presentation Model
  36. 36. Traits3. Helpers to Helpers
  37. 37. Traits4. Wanna be objects
  38. 38. Traits5. Type container
  39. 39. Traits6. Traits with standards
  40. 40. Implicits
  41. 41. Implicits
  42. 42. Implicits
  43. 43. Options
  44. 44. Tendency to have fewer testsRefactoring Code discoverability
  45. 45. In Retrospect …
  46. 46. Does it really speed up the development as was hoped?Should the projecthave been done in Java? Is it easier to maintain and extend than an equivalent Java code What features of the base? language and patterns of usage have been successes?
  47. 47. Scala compiler slower than Java’s
  48. 48. Questions

×