Skip to main content

Why Scala

1. Type Inference :

Uses type inference to allow the compiler to
infer the type of variables from the instances bound to them. We would write the
equivalent line in Scala as follows:
val myInstance = new Example()
The Scala compiler infers that myInstance has the Example type at compile time. A
lot of the time, it is enough to specify the types of the arguments and of the return
value of a function. The compiler can then infer types for all the variables defined in
the body of the function. Scala code is usually much more concise and readable than
the equivalent Java code, without compromising any of the type safety.

2. Immutable objects : Scala encourages the use of immutable objects.
val rollnos = List("720", "729") // List is immutable
rollnos(1) = "5" // Compile-time error
Knowing that some objects cannot be changed once instantiated reduces the number of places bugs
can creep in.

3.Functional Programming :

Scala encourages functional code. A lot of Scala code consists of using higher-order
functions to transform collections.

Comments

Popular posts from this blog

ASCII to Decimal conversion

#include "msp430.h"                     ; #define controlled include file         NAME    main                    ; module name         PUBLIC  main                    ; make the main label vissible                                         ; outside this module         ORG     0FFFEh         DC16    init                    ; set reset vector to 'init' label         RSEG    CSTACK                  ; pre-declaration of segment         RSEG    CODE      ...

Event Sourcing with CQRS.

  The way event sourcing works with CQRS is to have  part of the application that models updates as writes to an event log or Kafka topic . This is paired with an event handler that subscribes to the Kafka topic, transforms the event (as required) and writes the materialized view to a read store.