pavfarb

6 ms·

1.
by pavfarb 9y ago
So that's why Taleb deadlifts like a madman.
2.
by pavfarb 10y ago
The way I see it, Acra combines rather unique security guarantees in a very elegant way. More precise questions could fruit more precise answers, though
3.
by pavfarb 10y ago
Woohoo! I am one of the engineers behind the project, and can answer questions if anyone has any.
4.
by pavfarb 10y ago
"built-in JSON serializer/deserializer" near "closures" and "coroutines (via fibers)" feels a bit.. odd. Sign of the times, I understand, but still. Apart from this boring grumbling, the project is very i
5.
by pavfarb 10y ago
If we could avoid doing so - we would, because we understand how hard earned Go's guarantees are. But, things are the way they are.
6.
by pavfarb 10y ago
But, as he says, 'sometimes you have to'. This is a time like this.
7.
by pavfarb 10y ago
Well, it is true: it was interesting side effect that 'just worked', we were like 'hmm, if GC is able to control external memory allocation, well, fine, maybe Go is even better than we've thought initially'. At some
8.
Techniques for investigating untypical Go memory leaks(cossacklabs.com)
27 points by pavfarb 10y ago|9 comments
9.
by pavfarb 10y ago
It would, but the place where these techniques are helpful the most (untyped languages with problematic input sanitization) are the languages for which hurting intermediary performance is a minor offense: most of it is already wasted by lan
10.
by pavfarb 10y ago
Not so, regular engineers should write, it's a question of what they write. I'm a regular engineer, my colleagues are as regular boring folks as possible, yet we're writing stuff from time to time. Look, here's an exampl
11.
by pavfarb 10y ago
>I actually miss the days when engineers blogged more rather than accumulating karma on Stackoverflow. 100% hit. I do write sometimes on StackOverflow to give back some help to the wonderful minds over then Internet, because, sharing kno
12.
by pavfarb 10y ago
It's really unfortunate that people do read my comment as "engineers shouldn't write". Engineers should write. I actually write a lot of stuff, because I like it. There are some pieces of your own research you can't
13.
by pavfarb 10y ago
Writing is, publishing and noising the channels isn't. I'm afraid I find experimentation like that at cost of other people's time and attention to be a bit petty crime.
14.
by pavfarb 10y ago
Engineers should blog publicly when they have something to say. Something useful for their colleagues. Engineers shouldn't waste time forcing themselves to blog instead of work just to push their career forward: frequently they just ex
15.
by pavfarb 10y ago
If we think that intentional collision is not a threat vector, while, as life shows, it is: https://bugs.webkit.org/show_bug.cgi?id=168774#c23
16.
by pavfarb 10y ago
Now I really wonder what will happen to Git we all know and love.
17.
by pavfarb 10y ago
SHA1 use cases are not limited into integrity verification of documents, but used a lot for traffic integrity and generation of authentication codes: - Torrents of all kinds. - Version control systems (where ability attacks like displacing
18.
by pavfarb 10y ago
The whole idea of relying core security guarantee (provable 'no knowledge' on server side) on unreliable mechanism (in-browser cryptography) is feels really wrong. There are many services which attempt to base their security on in