knucklesandwich

15 ms·

61.
by knucklesandwich 10y ago
> Your privacy settings is a local concern to your account, it most certainly does not need to be globally consistent. All you need to do to avoid problems with that is to ensure consistency in routing requests for a given session, and e
62.
by knucklesandwich 10y ago
Apologies, you're right, I've never implemented bank accounting in the real world, I'm only talking about it in the sense of an account balance as a "toy problem", where its often used to discuss the virtues of weak
63.
by knucklesandwich 10y ago
> You misunderstand me, and I appreciate that I should have been clearer: A single observer in a single location that is both the sole observer and creator of event will have a consistent view. But this isn't a very interesting scen
64.
by knucklesandwich 10y ago
Apologies, I didn't mean it as a critique of your post. What I meant was that its often used as a strawman example of why you don't need consistency[1]. Bank transactions are extremely simple compared to the majority of things we
65.
by knucklesandwich 10y ago
> You design systems to make them self-correcting: Log events durably first, and then act on the events. If possible, make operations idempotent. If not, either make operations fully commutative, or group them into larger commutative ope
66.
by knucklesandwich 10y ago
The bank example really needs to die, its not reflective of what people often use databases for. 1. Bank transactions are easy to express as a join-semilattice[1], which means its intrinsically easy to build a convergent system of bank acco
67.
by knucklesandwich 10y ago
Federal funding generally comes in the form of grants and lending, not budget disbursement. So the states making budget cuts to schools (which may or may not be politically justified by increased lending and grants) is not the federal gover
68.
by knucklesandwich 10y ago
The paper even admits that it probably exaggerates the effects of grants and loans since their model doesn't incorporate private and public schools with different funding characteristics or competition[1]. [1]: http://www.nb
69.
by knucklesandwich 10y ago
Yeah, just reread how I worded this and it's not quite correct. Your points here about how all synchronous exceptions are handled the same is correct. I think what I was trying to get at was that exceptions in pure code are usually tre
70.
by knucklesandwich 10y ago
Haskell definitely has problems. I'm a huge fan of the language, but I think its disingenuous to pretend like its flawless. To name a few: 1. Poor debugging tools. Unfortunately this is sort of intrinsically tied with non-strict evalua
71.
by knucklesandwich 10y ago
> My point, which you've ignored, is that we need to take into account the wider context, i.e. "the last few years of speaker exclusions and anti-"brogrammer" activism" I mentioned. What does this even mean? It&#
72.
by knucklesandwich 10y ago
> Nodevember were told that having Crockford speak "sent a message that women are unwelcome". I saw the tweet, my point here is that's a single tweet raising a red flag about what is undoubtedly an issue that was talked ab
73.
by knucklesandwich 10y ago
William Golden and Jason Orendorff seem to be the only organizers in this discussion, and neither of them says anything more than "he was uninvited because other attendees and speakers did not feel comfortable attending/speaking w
74.
by knucklesandwich 10y ago
Even the thread you cited claims there were other speakers who came forward. Unless there's some public acknowledgement over what the deciding factors are, this is a lot of speculation over what little public conversation (on twitter a
75.
by knucklesandwich 10y ago
I'm just going to keep posting this until I see some recognition of this, but none of the details here or in the "In Defense of Douglas Crockford"[1] post from yesterday are actually called out in the Nodevember statement[2].
76.
by knucklesandwich 10y ago
> So you want to say, that there doesn't need to be a real reason anyway, it is just enough that a few other speakers have a problem with him. It doesn't even have to be made transparent what the problems actually is. No, what
77.
by knucklesandwich 10y ago
This is an awful lot of outrage over details that aren't substantiated by the Nodevember statement[1] or any cited sources whatsoever. [1]: http://nodevember.org/statement.html
78.
by knucklesandwich 10y ago
Some people in the developer community need to get better at recognizing when a witch hunt is brewing. This blog post has essentially the same content as the one yesterday on the same subject[1]. Like the one yesterday, it attempts to provi
79.
by knucklesandwich 10y ago
Totally agree. At a previous job, some of the senior engineers decided to use MongoDB as the main data store, and doing migrations was among the worst things about it. I think some engineers envision that they'll just be able to do rea
80.
by knucklesandwich 10y ago
Ah, bummer, yeah that's a convenient short term fix. It sounds like you all have this handled pretty well though, I think you'll definitely appreciate the move to a more traditional schema. For events data, JSONB support can be ni
81.
by knucklesandwich 10y ago
Totally agreed. Some people have an unreasonable fear of migrations (not to try to put words in the above poster's mouth, just pointing out something that I've noticed). You generally shouldn't worry about migration-related d
82.
by knucklesandwich 10y ago
Definitely have been bitten with the query statistics issue before. I worked with a colleague once who was adamant that we build our backend on MongoDB, but I was able to convince him to build on Postgres because of it's JSONB support.
83.
by knucklesandwich 10y ago
> Okay, then you can throw away the rest of your post and stop right here. The overwhelming historical evidence is that assembly doesn't scale. Huh? I'm not actually arguing that assembly is a scalable language. I'm invoki
84.
by knucklesandwich 10y ago
The advantage you're describing is concurrency, which doesn't necessarily require an asynchronous/event-driven programming model. Synchronous concurrency is built around threads to achieve concurrent execution (i.e. instead o
85.
by knucklesandwich 10y ago
FWIW, strictness may be introduced into haskell programs. Weak-head normal-form evaluation is builtin with the "seq" function and the "deepseq" library is commonly used for fully normal form evaluation of expressions. GH
86.
by knucklesandwich 10y ago
You'd have a point if the default with Go was a good choice. In practice its not. It's a terrible choice that gives you no ability to use multiple versions of a package (across projects), control a project's dependency's
87.
by knucklesandwich 10y ago
> Please keep in mind that there are differences at scale. What is "easy to work with" for 1 programmer over a month might not be so for 20 programmers over years. > The argument is that simpler is better at scale. Airplanes
88.
by knucklesandwich 10y ago
You can make this argument with nearly anything we naturally accept as a feature of a programming language. The ability to name things has a long history of abuse. The ability to define types, implement programming patterns, define new synt
89.
by knucklesandwich 10y ago
FWIW I'm not trying to strawman the argument behind not having features like this. Rob Pike said this in a talk about Go: "The key point here is our programmers are Googlers [...] They’re not capable of understanding a brilliant l
90.
by knucklesandwich 10y ago
The biggest irony of Go is that they have invariant parametric types for channels, arrays, etc. and indeed primops like channel sends, make, len, etc. are parametric functions. So for all the defensiveness about how parametric polymorphism

More ›