bkirwi

10 ms·

31.
by bkirwi 12y ago
It always seemed to me like the academic-style sabbatical was a nice solution to this. Instead of trying to convince a bunch of people that what you're going to do is going to be worthwhile, you develop a culture where capable people a
32.
by bkirwi 12y ago
Yes, that's the principal idea, I think -- separating out the implementation details from the actual conditions that are necessary for correctness. IIRC, I've seen another presentation of this where the author used that freedom to
33.
by bkirwi 12y ago
If you find yourself creating a throwaway just so you can criticize someone's coding style on a quick graphics experiment, you may want to reconsider your life choices.
34.
by bkirwi 12y ago
Not guilty! I picked this one up on Twitter this afternoon, but it's possible the lineage traces back to your lobste.rs post. (I have no lobste.rs account, though not for lack of interest -- while sparse, the comments there seem to be
35.
Learn You an Agda(williamdemeo.github.io)
127 points by bkirwi 12y ago|70 comments
36.
by bkirwi 12y ago
There you go.[0] I believe it's called the 'arbiter problem' in that context, and your description seems basically correct. [0]: http://research.microsoft.com/en-us/um/people/lamport/pubs&#
37.
by bkirwi 12y ago
var ( ch = make(chan *http.Response) err error ) .... return func() (*http.Response, error) { return <-ch, err } It seems to me like calling that returned function is destruct
38.
by bkirwi 12y ago
Thanks!
39.
by bkirwi 12y ago
Yep! You can trace that thread back to Lamport's work some decades back. The thing I find really compelling about this paper is that it's not tied to a single coordination method, though -- it pulls everything back to application
40.
Coordination Avoidance in Database Systems [pdf](vldb.org)
32 points by bkirwi 12y ago|5 comments
41.
by bkirwi 12y ago
If anyone's trying this at home, I'd suggest scoping down the problem a bit: - Trying to get rid of a specific problematic dependency? It's easy to filter a DAG to only those paths that lead to a particular node. - Trying to
42.
Plato and OOP(metaphysics.io)
2 points by bkirwi 12y ago|0 comments
43.
by bkirwi 12y ago
They are quite similar. As a longtime Finagle user: the most obvious difference is that Colossus is much more explicit about the event loop, and expects a lot of things to be 'local' to a single event loop. I expect this has non
44.
by bkirwi 12y ago
Presumably, Tumblr also uses Scala for the services themselves... and by assuming Scala, they can make the API more idiomatic. (For me, the question runs the other way -- I need a very good reason to write a codebase in Java vs. Scala these
45.
by bkirwi 12y ago
The big one is the recent add of the 'invokedynamic' instruction, which has dramatically improved the performance of dynamically typed languages.[0] Mostly, though, it's just externalities from the slowly-and-steadily-improvi
46.
by bkirwi 12y ago
Great to come across such an even-handed review; thanks! One quick note: > Other than cherry picking studies to confirm an long-held position, the most common response I’ve heard to these sorts of studies is that the effect isn’t quantif
47.
by bkirwi 12y ago
According to the manpage, the filename depends only on the supplied URL: Write output to a local file named like the remote file we get. (Only the file part of the remote file is used, the path is cut off.) The remote file name to use
48.
Coordination Avoidance in Distributed Systems [pdf](vldb.org)
2 points by bkirwi 12y ago|0 comments
49.
by bkirwi 12y ago
This is a nice article, but the title strays into 'Fox and the Grapes' territory. Exactly-once delivery is pretty much always what you want -- in contexts where all manner of delivery guarantees are possible, from Java's conc
50.
by bkirwi 12y ago
The 'he' seems not to be the most important part here. (Though, as the GP points out in another comment, the singular 'they' is useful.) The particularly nasty part is this: > And I eventually leave, because now they&
51.
by bkirwi 12y ago
I haven't dug through the paper yet, but this seems like a really nice result: both theoretically elegant and practically useful. Looking forward to working through the details.
52.
When Does Consistency Require Coordination?(bailis.org)
19 points by bkirwi 12y ago|1 comments
53.
by bkirwi 12y ago
Kafka is a Big Deal, and it's great to see it get first-class support. In the same way that Hadoop is starting to feel outdated, but HDFS doesn't seem to be going anywhere -- I think we'll see a lot of innovation in stream pr
54.
by bkirwi 12y ago
Sure! Let's take the immediately preceding example, where the author had a black woman as a supervisor. The author describes this as 'diversity lightning'. If you interpret this narrowly, this makes absolutely no sense: there
55.
by bkirwi 12y ago
Startup idea: create a CAPTCHA that humans recognize as one word, but OCR recognizes as a different word.
56.
by bkirwi 12y ago
If you do any reading on race and diversity, you'll come across the idea of racism as a systemic thing -- racism not as single instances of discrimination based, but a recurring pattern. This is why it's very hard to insult a whit
57.
by bkirwi 12y ago
This is absolutely right. I suspect some people do this because Twitter went out of their way to get 64-bit ids[0] -- but Twitter did this in large part because they made the mistake of baking that bit-length into the protocol back when the
58.
by bkirwi 12y ago
It's 1 in a million chance of any collision across the entire dataset, not 1 in a million records that will have a collision. This is why the article mentions the birthday paradox -- it's taking the chance of a collision between
59.
by bkirwi 12y ago
TBH, I think that is a legitimate technical nit. Case classes end up being very useful, but they're not as principled as the ADTs that they're generally used to replace, and that shows up in a bunch of weird corner cases. It'
60.
by bkirwi 12y ago
You might prefer Kotlin?[0] It's going in the same direction as Scala, but not quite so far. By the way, I'm curious what you mean by "the semantic confusion between the Option type and sequences that leads people to map over

More ›