Let’s talk about PyPy…

Advertisements

A small rant about software reliability…

“I’m very serious about software reliability, and this is not just a good thing. It is good in a sense, as I tend to work to ensure that the software I release is solid. At the same time I think I take this issue a bit too personally: I get upset if I receive a crash report that I can’t investigate further for some reason, or that looks like almost impossible to me, or with an unhelpful stack trace. Guess what? This is a bad attitude because to deliver bugs free software is simply impossible. We are used to think in terms of labels: “stable”, “production ready”, “beta quality”. I think that these labels are actually pretty misleading if not put in the right perspective…”

http://antirez.com/news/43

BigData using Erlang, C and Lisp to Fight the Tsunami of Mobile Data

“The solution uses:

  • Less than 20 large instances running on Azure
  • An in-memory database
  • A full blown custom LISP language written in C to implement queries, which is many times faster that having a VM (with a garbage collector) online all the time
  • Erlang for communication between nodes
  • Modified TCP_TIMEWAIT_LEN for an astonishing drop of 40K connections, saving on CPU, memory and TCP buffers…”

 

http://highscalability.com/blog/2012/11/26/bigdata-using-erlang-c-and-lisp-to-fight-the-tsunami-of-mobi.html

Thoughts on immutability in D

“Const/immutability in D is great just as it is. I’ve been through the pain of finding non-deterministic bugs in multi-threaded code, so I really appreciate D’s guarantees. I can see his point in liking the idea of a weaker logical single-threaded const. I don’t see any reason why an escapable logical const shouldn’t exist in D in the future, but then I don’t design compilers or languages…”

http://www.reddit.com/r/programming/comments/knn5p/thoughts_on_immutability_in_d/