Welcome to this week issue of Scalac Weekly Digest. We hope you enjoyed the last issue, because this time we have more cool things to share with you. In this edition we will share with you some tricks in Scala and Clojure, show you a neat project created by researchers at DARPA, help you understand Event Sourcing better and complain a bit about Docker. We hope you enjoy it. See you next week.
Interview with Andrew Jayne, senior software developer at McLaren Applied Technologies. Read the article if you want to know why they chose Scala for data analysis tools in Formula 1 industry.
This blog post explains what Abstract Algebraic Data Types are and how we can use and implement them in Scala.
We live in a world where technology gives us endless possiblities. Project HAPTIX aims to help people who lost their limbs and have to live with prosthetic limb systems. Researchers at HAPTIX want to make those prosthetics more like natural body parts by providing a way to “feel” with the artificial body part.
Set of links to articles which provide interesting information about Clojure language. If you are at the beggining of the Clojure-programming-way this article will be very handy.
Maybe these reasons will help you with choosing Clojure as the next language to learn?
This article describes core issues you may face when designing event-sourced system in a distributed environment. The architecture of a lightweight re-implementation of akka-persistence API is outlined shortly. Among others, it covers concerns such as preserving happens-before relationship and conflict resolution.
The author of this blog post used Docker when it was 1.0 and disliked it for multiple reasons (usability, purpose, security and more). But as time went by, he wanted to give a chance to Docker once again. Take a look to see if Docker is ready for production and where it should really be used.
Interesting comparison between Docker and Virtual Machines applying to real world problems and differences in usage of both.
Most of programmers write unit tests. We do that to improve the quality, find bugs when they occur and to prevent regression. But how do we know that the tests that we are writing are helpful and really do what intended? Mutation testing is a handy tool that allows us to validate our tests and make sure they aren’t just noise