Disclaimer: this article is a translation. Original post was published in June, 2015. The first part is here. Let’s go on. For seven f*cking years, I’ve been waiting for a programming language that would meet my requirements. During this time, I’ve tested everything. Everything means all the general-purpose crap and all the not-quite-general-purpose crap. You can’t feel a language only by reading about it and writing “Hello, World!”. To understand the language, you should write at least something with it.
This article is based on Your Language Sucks in the form of half a joke. In the mentioned article, most of the “problems” are either synthetic and rarely used, or far-fetched due to expectations of the language correspondence to a theoretical paradigm the language should correspond to. On the other hand, the article misses a few things that really complicate my life as an engineer. I’m not claiming to have an absolute knowledge of Kotlin, so there can be some mistakes in the article.
Since I’m going to provoke trolls on the subject of programming languages, and even name the best one in the world (I mean absolutely the best, for sure), I recommend all of them to check out my previous post “Choosing a Programming Language”. Everything mentioned there is still up-to-date, and I wouldn’t’ like to repeat myself here. Read it? Good. Today I am going to talk about the best programming language in the world, and I’ll name it closer to the end of this post.
There are plenty of technologies to organize parallel computing. One of the most promising and simple ones is the model of actors. It allows to partially get rid of such major problems of parallelism as race conditions, locking waits of operations termination, endless mutual exclusions and synchronizations, and so on and so forth. This approach also simplifies the code paralleling. We are going to review it by the example of akka framework using Java language.
Java 8 has been recently released. So I decided to write something using its new features. Namely the new collection api, which allows to work with collections in a more functional style, and default methods in the interfaces. This article is a brief review of my experience of Java 8, Spring MVC, Hibernate and SSP integration. Foreword I’ve always admired the Scala language. First of all, because of the binding with external libraries (Hibernate, Spring, Spring MVC), which I still have a weakness for.
