I am quite conservative with what I install on my computer. Even more so when it comes to installing package some package manager just to be able to use one package hosted. I have been meaning to play with Elm for some time and it was disappointing to see the requirement of npm, in addition to a source install, to use it on GNU/Linux. Of course I have been misreading the following statement:
Second, if you are on some linux OS and just want to use Elm, use the npm installer.
Have you read Out of the Tar Pit? If you have not, please do so before reading this post so it would make sense. Actually you can just read that paper, there is nothing nearly as useful here. I will just be ranting on my side project that implements the system described in the paper for the next couple hundred words.
This is the second part of the guide to integrate Scala code from Java. You can read the first part here.
This post is about extending Scala classes and traits and also accessing the Scala object‘s (singletons).
This is the first part of a guide to integrate Scala code from Java. It can be considered as the dual of Scala Tutorial for Java Programmers, which guides Java programmers write Scala code. My aim is help programmers writing Java code that deals with Scala objects (as in JVM objects, not necessarily Scala object‘s).
TL;DR: schema implementation is fixed & validation-benchmark report is now hosted on GitHub Pages.