cakoose

25 ms·

211.
by cakoose 11y ago
I think the parent was assuming a lovely world where all passwords would be large randomly-generated strings. In that case, salting is no better than just increasing the size of the randomly-generated string, right?
212.
by cakoose 11y ago
I couldn't quite follow. Are you disagreeing with anything OP said?
213.
by cakoose 11y ago
Oh, that makes sense, haha. While reading it I was like "why is this journalist so blindly positive about this new system?"
214.
by cakoose 11y ago
"No one particular project should be considered a 'distributed social network'" What? Something can be a distributed without being interoperable. This article is humorously unbalanced. Sounds like someone venting. E
215.
by cakoose 11y ago
But isn't volume-based pricing a good approximation of cost-based pricing? With the new setup, are low-volume customers paying extra to subsidize high-volume customers?
216.
by cakoose 11y ago
I can sympathize with the Washington Post. There are two common uses for the word "impossible" that are relevant here. Solving the halting problem is impossible in the absolute sense. We have a proof. But think about the (mind-b
217.
by cakoose 11y ago
Any idea how it compares to CurveCP [ http://curvecp.org/ ] and Noise [ https://github.com/trevp/noise/wiki ]?
218.
by cakoose 11y ago
> Your method doesn't follow the same format as the rest of Go's syntax (eg comma delimited lists) which could break any 3rd party pre-parsers or other such tooling. So there's the potential break backwards compatibility
219.
by cakoose 11y ago
But it looks like Go has done similar things in the past. For example, the slicing operation gained an additional optional argument ( https://golang.org/doc/go1.2#three_index ). It's not exactly the same thing, bu
220.
by cakoose 11y ago
On slide 9 it says that enhancing the syntax for "import" would be a backwards-incompatible syntax change. Sure, old compilers wouldn't accept newer code, but newer compilers would accept old code without breaking the behavi
221.
by cakoose 11y ago
It's not just the behind-the-scenes stuff that's ugly. Whatever they used to render the text is much worse than what my browser does. And there's no mouse hover changes. And you can't copy/paste the text. Follow
222.
by cakoose 12y ago
Ugh, that didn't go as planned. 1. Sorry to everyone about the "his". Like most people guessed, I explicitly tried not to use gender, but I slipped up. 2. I didn't mean to imply you were bad at programming. The only go
223.
by cakoose 12y ago
The author spends a lot of effort trying to make his functions point-free. For example, the author first writes: inexactMatches xs ys = matches xs ys - exactMatches xs ys then decides it's not very "nice", and ends
224.
by cakoose 12y ago
Reminds me of the differential gear in cars and what happens when one wheel is up in the air with no traction.
225.
by cakoose 12y ago
Two things. First, I think it's more about the initial reaction to Go, from someone coming from Rust (or Java, C#, C++, etc). But even so, I agree the wheels analogy is too extreme. I'd maybe say that it's like hearing that
226.
Ask HN: If you're “ridiculously in love with Python”, do you even know it well?
46 points by cakoose 12y ago|40 comments
227.
by cakoose 12y ago
I agree. It's a fun quote and has humor value, but it's the exact wrong stance to take when thinking about security. Stupidity is one of the most commonly used disguises for malice.
228.
by cakoose 12y ago
Fossil's bug tracker is not just a separate system bundled with Fossil. The bug database is integrated with the VCS for a reason. Edits to the bug database are tracked, branched, and merged the same way source code is. For example, l
229.
by cakoose 12y ago
Let's say you start with a small array, then add N elements, one by one. When you run out of space in your underlying, you allocate a newer array, copy all the elements over, then free the old array. If your new array is always a cons
230.
by cakoose 12y ago
OAuth is basically two decoupled things: the request authentication format and the app authorization flow. Request authentication in OAuth 2 is typically done by adding the HTTP header "Authorization: Bearer <access-token>"
231.
by cakoose 12y ago
Paul Phillips' 2013 rant/talk: https://www.youtube.com/watch?v=TS1lpKBMkgg
232.
by cakoose 12y ago
You're example is not a static typing issue. It's a feature of the library that the struct field doesn't have to have the same name as the form field. I think the issue is more of a DRY thing, which could maybe be fixed with
233.
by cakoose 12y ago
Deeper in the site they have a benchmarks page[1] that has a short "why not Cap'n Proto": "Cap'n'Proto promises to reduce Protocol Buffers much like FlatBuffers does, though with a more complicated binary encod
234.
by cakoose 12y ago
You can make it so that finding a free slot is always O(1). Keep another array that is a stack of available slot indexes. When you need a free slot, pop off an index and use that slot. When you're done with a slot, push its index on
235.
by cakoose 14y ago
These are excessively detailed numbers with very little context. What is the code doing? What's the performance of the equivalent implementation in another language (I'd be most interested in a typed language like Java)? I realize you pro
236.
by cakoose 14y ago
It's not severless. Jerks.
237.
by cakoose 15y ago
I think he's taking a widely-accepted idea -- that the C++ language is a complicated language -- and making the unfounded leap that most C++ code is just as complicated. For starters, the standard C++ string type is reference-counted, somet
238.
by cakoose 15y ago
This paper uses cooperatively scheduled threads (i.e. no preemption or concurrent execution of threads), which means you don't have to deal with synchronization.