Scala: The Ideal Language for Game Wallets

Transcript

1. Scala: The Ideal Language for Game Wallets
2. Game Wallet needs to work well.
3. Scala JVM runtime statically typed multi-paradigm
4. Scala is descriptive strongly typed type aliases case classes pattern matching
5. map Transforms collection of elements by applying function to every element
6. Self-explanatory definitions weakly-typed example:
7. Self-explanatory definitions scala example:
8. Type aliases
9. Type aliases
10. Type aliases
11. Type aliases
12. Type aliases
13. Robustness The ability of a program to tolerate faults and handle incorrect input
14. Scala is robust compile-time type-safety effective error handling
15. Refined types fails with compilation error:
16. Refined types
17. Error handling: Option[A]
18. Error handling: Either[E, A]
19. Error handling: Either[E, A]
20. Fearless refactoring
21. Fearless refactoring
22. Scala is multi-paradigm OOP FP
24. OOP: case classes
25. case class: pattern matching
26. case class: pattern matching
27. mutating shared state I/O throwing exceptions FP: no side effects Side effect: when function relies on or modified something outside its parameters.
28. composable testable easy to reason about FP: pure functions Pure function: function that doesn't perform side effects.
29. Multiple runtimes JVM: most widely-used runtime for Scala Scala Native: faster start-up time, lower memory footprint JavaScript: for Scala.js
30. Scala on JVM inter-op with java libraries existing performance tools VisualVM, JConsole, etc. can interact with java sources
31. Scalability The ability of program to expand or adjust to higher load
32. Scala is scalable effect systems & fibers akka & actors functional concurrency operators & primitives
33. Effect systems Effect systems are used in functional programming to manage side effects. They help to manage unpredictable program parts such as mutating shared state, I/O. In scala most popular effect systems are cats-effect and ZIO. Besides that - effect systems come with runtime for managing concurrency. cats-effect runtime provides thread pool for: computation tasks blocking operations
34. Fibers Fibers are extremely lightweight threads. In JVM runtime - they run on top of JVM threads. Based on cooperative multitasking (instead of pre-emptive like e.g. OS) Semantically blocking (doesn't block underlying thread) Purely functional composition, timeouts, cancellation
35. Fibers: parallel combinators we end up with 100 fibers just for the region enclosed within 'parTraverse': they're all in WAITING state and they're not blocking any real thread.
36. Fibers: result type
37. Fibers: Errored
38. Fibers: Canceled
39. Scala is stable Java released in 1996 Scala in 2004 seamless inter-op with java
40. linktr.ee/mbednarz