zniperr

5 ms·

1.
by zniperr 8y ago
Ah, I thought you were referring to HWAsan with the 35%, hence the confusion.
2.
by zniperr 8y ago
Paper author here, thanks for the interest :). I just wanted to elaborate on the overhead numbers you mentioned. I am not specifically familiar with the 35%+ numbers, but you should take into account the cost of any defense on top of the co
3.
by zniperr 11y ago
In "Parameter Selection" you say "We simplify this by having service owners define the current number of outliers, if there are any, at configuration time." How do service owners get this data? by manual inspection of gr
4.
by zniperr 12y ago
I have the same issue on Chrome 40.0.2214.111 on Linux. Other than that I agree, it's nice to have multiple alternatives for different purposes. For example, there is also Skeleton ( http://getskeleton.com/ ) which has a
5.
A Brainfuck to binary compiler using LLVM, written in OCaml(github.com)
1 points by zniperr 12y ago|0 comments
6.
The difference between top-down parsing and bottom-up parsing(qntm.org)
81 points by zniperr 12y ago|43 comments
7.
by zniperr 12y ago
The examples are very relatable, at least for me personally. Judging from this fragment, I would consider myself a stack person: "For tasks that represent pain that must be immediately alleviated, it’s not that the stack feels I must
8.
by zniperr 12y ago
At first glance this seems to be for Python what Coffeescript is to Javascript, and I love Coffeescript (mostly). I would be interested to see some performance comparisons with regular Python.
9.
by zniperr 12y ago
By the way, I do think pattern matching could have been discussed more extensively. Pattern matching is one of the reasons I love functional programming so much, since combined with algebraic types they can be much more expressive than impe
10.
by zniperr 12y ago
A good read, I especially like the parts about error handling and maps/applicatives. They are well-illustrated and tackle some difficult common problems I had shortly after I started using functional languages. The part about functors&
11.
by zniperr 12y ago
Nice explanation, the overall layout and text-to-code ratio make it easy/fun to follow. I would like to see the finished post when all the TODO's are filled in. I would suggest to add "AMD64" explicitly to the page title
12.
by zniperr 12y ago
So, I just completed the "curiosity killed the mouse" level, took 3 people a while to realise what was going on, but after a few minutes we got to the non-obvious solution, and I got sent back to the first level. I feel a bit scre
13.
by zniperr 12y ago
A difference is that a GPU uses a lot of power and takes up a lot of space. I can imagine an optimized, energy-efficient chip would be useful in embedded systems. Something like a Raspberry Pi for image processing maybe?