Perl6 also has gradual typing system that allows it to not only type-check but also to optimize the byte-code when types are specified
Interview loops - hiring Scala developer in Dublin - it’s hard in fact.
This week in Scala; http://www.cakesolutions.net/teamblogs/this-week-in-scala-19/01/2015
It looks, at best, like an extremely limited reinvention of that wheel…as a square. Looking through the contents of the repo, it’s clear the author has basically no clue about sane organization of C code (basically all the code, including non-extern global variable declarations, is in header files for one thing). Note that the submitter’s one other submission is pretty similar-looking – an incompetently-done, crippled version of tcpdump.
Can we please, please have a low-quality downvote option? Please?
Adding transparent LZ4 and Deflate compression to akka-kryo-serialization and along the way adding tests and improving the performance for maps and sets.
Already done: my pull request to fix the recent LZ4 vulnerability was merged today in lz4-java.
Links: https://github.com/luben/akka-kryo-serialization https://github.com/jpountz/lz4-java
This is a very interesting project! Given that it’s a strongly consistent distributed KV store, it seems very similar to ZK but supporting larger datasets?
Could anyone comment on how this differs from ZK?
Actually, ZK is eventually consistent as well. It even has the same notion of followers (called observers) http://stackoverflow.com/questions/3662995/explaining-apache-zookeeper
ZK is not eventually consistent. If you always sync and then read, you will be sequentially consistent. You can fake eventual consistency by using fast reads only. ZK has its own version of paxos (zab) specifically to guarantee sequential consistency.
I agree with you that ZK is linearizably consistent in its core, however, it used to say that it was eventually consistent on its page.
It seems to me that Sirius has the same consistency model as ZK. I still am not seeing how it differs from ZK.
I am trying this week to distribute (using Akka actors) a streaming aggregation engine I have written in Scala. I have figured out last week what the components are and how they interact,now it is just matter of coding.
This reminds me of https://metacpan.org/pod/Acme::Bleach - it is not trickery with detecting ttys but encodes your program using only spaces.