barakm

11 ms·

61.
by barakm 11y ago
This is also reasonable; but an example of how schema get created and discovered by a client would be a nice extension to the spec. :)
62.
by barakm 11y ago
I've been looking forward to this! One question; it appears as though the types and schema are passed with every request (eg https://github.com/graphql/graphql-js/blob/master/src/graphq... ) --
63.
by barakm 11y ago
Forget the haters, this is awesome. GNU started as GNU's Not Unix, reimplementing Unix userland for free. The people who are adamant about calling it GNU/Linux are, on some level, remembering that the userspace is historically a r
64.
by barakm 11y ago
Not bad, at least a fair look! One thing that immediately set off my radar (as a Go programmer) is the paintingLoop switch on type. Yes, sometimes a switch on type is necessary. However, this is not one of those cases. You want to have a Tr
65.
by barakm 12y ago
To your first question: https://github.com/coreos/etcd/milestones (and the mailing list is pretty useful as well, to keep up on point releases and announcements and such). To your second question, Kelsey said it b
66.
by barakm 12y ago
I can safely say that's not the case. Much of what we're doing with CoreOS or Tectonic depends on open source, particularly our open source projects. That's not going away anytime soon. (etcd dev here. We've got a long r
67.
by barakm 12y ago
Very much so! I'd love some help writing/documenting/explaining to people a lot of the work I've done behind Cayley ( http://github.com/google/cayley ). I can explain it very well one-on-one or to a d
68.
by barakm 12y ago
So I tried it. I successfully lost data, and reported conflicting/inconsistent data, with a one-line change to your example to-do list. Instead of generating a key that won't conflict, I force it to write to the same key. Yes, thi
69.
by barakm 12y ago
The problem with AP is that you completely lack consistency guarantees, and most people will agree that's a bad thing. That you advocate that notion so heavily, and without scholarly research makes me really, really nervous. From what
70.
by barakm 12y ago
From the blog: > Because gun is not a database (NoDB), it is a persisted distributed cache. This I believe. > The fatal flaw with databases is that they assume some centralized authority. While this may be the case initially when you
71.
by barakm 12y ago
How about not existing? Seriously, this was originally 0.5. However, because people had started to use 0.4.6 as a pseudo-1.0 in production, and because the internals are completely different, it's a little bit of version jumping to a b
72.
by barakm 12y ago
One new 2.0 feature you may like (discovery wise) is SRV discovery, if you've got an internal DNS/dnsmasq or something. Set a few records for where machines can be found (and keep them appropriately up to date) and it'll do t
73.
by barakm 12y ago
This would certainly help. High CPU was also an issue that we started to notice on 0.4.6, here with some of the NYC CoreOS guys, and that's been fixed. Chalk it up to completely redoing internal communication. EDIT: Master election too
74.
Announcing the etcd 2.0 Release Candidate(coreos.com)
24 points by barakm 12y ago|1 comments
75.
by barakm 12y ago
@markbao -- I did get Cayley out the door ( http://github.com/google/cayley ) which has many many parallels to Freebase's graph database, loading and storing Freebase data (as well as whatever other graph data). I&#
76.
by barakm 12y ago
Any links for the curious?
77.
by barakm 12y ago
If it fails in interesting ways, let me know, file a bug, etc. I'm more than happy to help.
78.
by barakm 12y ago
http://cayley-graph.appspot.com is a live demo on App Engine.
79.
by barakm 12y ago
It does have bulk import; I've been loading largish subsets of the Freebase dumps. Load speed is pretty good (into persistent storage, I assume) and can be improved with some of the database parameters. A rough estimate is that a milli
80.
by barakm 12y ago
I wanted something easy to pick up -- Javascript seemed natural. I also wanted to be as agnostic as possible, because graph query languages are interesting and worth experimenting with. That's why it has submodules per-language and it&
81.
by barakm 12y ago
Exactly this. And I'm the Googler. Hi!
82.
by barakm 13y ago
bool({}) should raise an exception, if we're being strict. You could try to define the addition of keys like you suggest, but you need to force a value type which defines a + operation into the same type. Which is what Counter() does
83.
by barakm 13y ago
Came here to say this. It's the most useful statement in the entire thread of "you're wrong!" "no, you're wrong!" and nobody noticed.
84.
by barakm 13y ago
"In communities which depend almost entirely on a single industry, such as a factory or mine, maintaining economic balance is a challenging problem." Almost a throwaway line, and of course, propaganda and dated -- but the Silicon
85.
by barakm 13y ago
As another commenter already pointed out, a common pattern is for people to try such a configuration, and end up starting again from scratch because, frankly, it doesn't work for them. Emphasis on "for them". I'm not say
86.
by barakm 13y ago
True! You could do that too. Sending the codebook is a cromulent strategy. It'd be lossless too. That's (to a first order) how LZ works. I was arguing you can use a standard codebook (some agreed-upon top-N list) instead. I imagin
87.
by barakm 13y ago
For fun, using @theosanderson's Up-Goer Five editor, my take at the balcony scene: http://bit.ly/ZY0wzk What's amazing is how little I actually had to change!
88.
by barakm 13y ago
As some comments are arriving below -- lossy compression does not work that way! Interpreting one set of data as another is a clever trick for puzzles (thematic, for example, to: http://web.mit.edu/puzzle/www/2013&
89.
by barakm 13y ago
This is pretty damn cool, but I can think of a few things that I'm curious how you're going to address: 1) Your C++ example, we have "namespace 'v8'" -- which has been removed and reinserted. That made me scratch my head a bit. Has it been
90.
by barakm 14y ago
When you start assigning context to statments, you'll quickly find yourself walking down the path to structured data, and toward the very complexity you're arguing against. At least predicate-wise. You'll then need to start assigning contex

More ›