Malbolge is a public domain esoteric programming language invented by Ben Olmstead in 1998, named after the eighth circle of hell in Dante's Inferno, the Malebolge.
Weaknesses in the design have been found that make it possible (though still very difficult) to write useful Malbolge programs.
Greedy algorithms for subgraph pattern matching operations are often sufficient when the graph data set can be held in memory on a single machine. However, as graph data sets increasingly expand and require external storage and partitioning across a cluster of machines, more sophisticated query optimization techniques become critical to avoid explosions in query latency. In this paper, we introduce several query optimization techniques for distributed graph pattern matching. These techniques include (1) a System-R style dynamic programming-based optimization algorithm that considers both linear and bushy plans, (2) a cycle detection-based algorithm that leverages cycles to reduce intermediate result set sizes, and (3) a computation reusing technique that eliminates redundant query execution and data transfer over the network. Experimental results show that these algorithms can lead to an order of magnitude improvement in query performance.
An eight year old child could use the REPL. If a child can type 2 + 2 into a REPL they are programming in Scala. Of course they could use a calculator, but if they do it in a REPL, they are using a scalable tool that can scale up for them from the simplest programming tasks to the most complex. unfortunately at the moment most mobile phones don't come with an easily accessible Scala REPL. But hopefull than can be fixed.
functional programming appeared long ago in the 50ies and developers in the 60ies and 70ies preferred to use OO instead. But you don't know why, do you? DO YOU? They did use OO because they were a bunch of hippies that didn't take anything seriously. They were that sort of people that went to Woodstock, got high on LSD and had brain damage after that. No, don't take this whole OO stuff seriously. We are finally getting back to reality now. Functional programming and NoSQL databases are definitely the best approach for software development.
Haven't you heard that functional programming is a MUST DO and just retards and programmers from the 80ies and 90ies use relational databases. Functional languages, NoSQL databases... Repeat with me. Functional languages, NoSQL databases. What a douche bag.
230 slides on High performance network programming on the jvm <slideshare.ne> by Urban Airship's Erik Onnen. I think the C++ version could be done in 100 slides. But really, very thorough and very good.
This should be required watching for anyone who cares about the future of efficient distributed programming: aside from the fascinating work he and his colleagues are doing, Neil is an excellent presenter and does a great job of distilling abstract computing concepts into something developers might actually be able to apply in production. vimeo.com
Developers are increasingly choosing datastores that sacrifice strong consistency guarantees in exchange for improved performance and availability. Unfortunately, writing reliable distributed programs without the benefit of strong consistency can be very challenging.
In this talk, I'll discuss work from our group at UC Berkeley that aims to make it easier to write distributed programs without relying on strong consistency. Bloom is a declarative programming language for distributed computing, while CALM is an analysis technique that identifies programs that are guaranteed to be eventually consistent. I'll then discuss our recent work on extending CALM to support a broader range of programs, drawing upon ideas from CRDTs (A Commutative Replicated Data Type).
Мои явапрогромисты напрогромировали так, что 6MB/s продакшн трафика каким-то образом не могут в постгрес и для его обработки поставили hbase кластер из пяти нод!
6 мегабайт в секунд! хайлоад! ъ-прайз! мегабайты xml конфигов! серьезные ебла!
While I concede that one can, in principle, solve a particular, confined problem more efficiently by doing absolutely everything by hand (memory management, scheduling, arithmetic), in the overwhelming majority of cases the demands of evolution of code far outweigh the potential advantages of doing everything by hand. Modularity matters most when it comes to building and evolving large systems; functional languages, with persistent data structures, support modularity the best.