thirsteh

22 ms·

151.
by thirsteh 13y ago
Most API requests are signed (using HMAC) with the API secret key, and do not actually include it, so no, probably. But certainly many other things could have been read if they were vulnerable.
152.
by thirsteh 13y ago
The ride home must be fun!
153.
by thirsteh 13y ago
It would be if SSL was expensive. It isn't.
154.
by thirsteh 13y ago
Okay, it appears we fundamentally disagree, so let's end the discussion here.
155.
by thirsteh 13y ago
> So it's 9 times of ten if you know what you are doing, which is hardly the most often case. If you don't at all know what you're doing, you're gonna fail every time, anywhere. It is obviously subjective, and I don&#
156.
by thirsteh 13y ago
I'm not trying to say you can't make errors in Haskell, just that, if you know what you're doing, slip-ups are extremely rare in the language. (Hence "9 times out of 10.") It's true, to some extent, with other
157.
by thirsteh 13y ago
Indeed. I'm not a fan of 100% code coverage tests in any language, but it's especially apparent in Haskell where, as you said, if code compiles (and you keep most of your functions pure), there are whole classes of bugs that simpl
158.
by thirsteh 13y ago
Completely agree. 9 times out 10, something compiles and works as expected, and can stay working in production for years. I don't know of any other language where I can do this and keep developing (and prototyping) the codebase. (This
159.
by thirsteh 13y ago
This is really quite silly since the choice between NullPointerExceptions and space leaks is a false one. You can have both in either language.
160.
by thirsteh 13y ago
FWIW, Simon Peyton Jones agrees laziness isn't the boon it's made out to be. While not universal, I feel confident stating that the opinion is shared by the majority of long-time Haskell programmers.
161.
by thirsteh 13y ago
Right, to fully evaluate something you'd use Deepseq. With data structures like Data.HashMap.Strict, Data.Text, etc., the HNF gained from strict data fields tends to be sufficient to avoid most issues caused by space leaks -- but even
162.
by thirsteh 13y ago
> laziness always seemed an important part of Haskell's elegance It's part of it, but to a lesser extent than you would expect. The much more important part of Haskell is its no-corners-cut separation of effects, which happened
163.
by thirsteh 13y ago
The choice between NullPointerExceptions or occasional space leaks isn't really apples-to-apples. You could similarly ask if you'd rather have solely impure functions and no isolation of effects, or occasional space leaks. Clearly
164.
by thirsteh 13y ago
700 MB runtime implies every compiled binary is 700+ MB, which is obviously untrue. You probably mean the compiler and standard libraries.
165.
by thirsteh 13y ago
Right -- I wasn't sure whether F# would be considered "practical" in this case.
166.
by thirsteh 13y ago
> Now, that begs the question, why lazy by default and not opt-in lazy? Very good question. Actually, I think most haskellers agree that laziness complicates things more often than not, and if we could start over we wouldn't make Ha
167.
by thirsteh 13y ago
I think there may be some confusion about what a space leak in Haskell is. When you apply a function f to a, that is not actually evaluated. Rather, a "thunk" is created that will evaluate `f a` only when that value is actually ne
168.
by thirsteh 13y ago
> Scala steals a whole lot of things for Haskell, trying to make it actually practical. LINQ is "practical Haskell," so is most of Rust (if "practical" means approachable to imperative programmers.) Besides being on t
169.
by thirsteh 13y ago
If you take a little care to e.g. make data types' fields strict, this tends to be a non-problem. It is harder to debug the code since it is lazily evaluated (and it's not imperative!), but recent versions of GHC provide pretty
170.
by thirsteh 13y ago
Indeed. They seem to be switching out and tunable unpredictable memory access (i.e. have to spend a lot of money building an ASIC with a lot of die area -- see the scrypt paper to understand why: https://www.tarsnap.com/scry
171.
by thirsteh 13y ago
Hopefully the CDC is a little more thorough than simply asking parents if their kids are autistic.
172.
by thirsteh 13y ago
The point of scrypt isn't really to be "ASIC-resistant", but to make it much more expensive to build ASICs to efficiently reverse its outputs.
173.
by thirsteh 13y ago
> You are arguing the wrong thing. > Here we are telling you to ignore his personal opinion. I don't know how to argue with that. You seem to think I'm the lone person who disagrees that his "opinion" is irrelevant
174.
by thirsteh 13y ago
CTOs rarely sit on boards.
175.
by thirsteh 13y ago
> If Brendan Eich today discriminate gay employees or volunteers he will be under a public crisis and he will lose his hard work. The reason why he is receiving so much criticism right now is that a lot of people don't think the dat
176.
by thirsteh 13y ago
I would say the president of the foundation (/the board) is analogous to the electoral college :)
177.
by thirsteh 13y ago
We are not in agreement.
178.
by thirsteh 13y ago
$100k is a pretty trivial amount of money to anyone whose career made them a billionaire. The amount, as a donation to deprive people of the rights that others have, is non-trivial to me, although it may very well be trivial to many others.
179.
by thirsteh 13y ago
Opinion, yes, but that is not what this is. We know with absolute certainty that he donated a non-trivial amount of money to block gay marriage legislation in California. That is an action solely intended to deprive a people of the rights g
180.
by thirsteh 13y ago
I'm saying that, while that might fly as CTO or any other role of the organization, CEO is a role analagous to President. The personal views of the chief executive very much influence the entire organization, and therefore it should no

More ›