redbad

5 ms·

1.
by redbad 12y ago
You should probably go back to your "well payed job".
2.
by redbad 12y ago
"I really like JavaScript" might be a compelling personal narrative, but it makes a pretty uninteresting submission to Hacker News :(
3.
by redbad 12y ago
1. There is a difference between voting for something and funding it. 2. There is a difference between being employed by a company and being its CEO. 3. These differences are significant.
4.
by redbad 13y ago
This is almost exactly how a plot device in Neal Stephenson's REAMDE plays out. In almost exactly the same part of the world. Bizarre.
5.
by redbad 13y ago
The code is super awkward, I'm pretty sure buggy, and unfortunately illustrates that the author has only a superficial understanding of Go idioms :(
6.
by redbad 13y ago
Agreed. In particular, I found the "reference value" approach that Go uses for time parsing incredibly quirky, but ultimately intuitive and unambiguous. http://golang.org/pkg/time/#Parse
7.
by redbad 13y ago
It seems that antirez believes he's allowing Redis to approach AP and/or CP semantics by providing primitives that users can compose in ad-hoc ways according to their requirements. Unfortunately, that's not a valid methodolog
8.
by redbad 13y ago
The NSA has nothing to do with the parent's proposal. Your entire reply is a non-sequitur.
9.
by redbad 13y ago
> Humans use <todo>. Indeed.
10.
by redbad 13y ago
> Are you suggesting that it isn't in Emacs? Yes, of course. Emacs is obviously and inarguably not immediately intuitive.
11.
by redbad 13y ago
There is no reason why "editing plain text" should be anything other than immediately intuitive. Advanced, time-saving features, like multi-cursors or regexp-based find-and-replace, can and should be progressively revealed through
12.
by redbad 13y ago
Text editors appear to be approaching a design ideal. At least, for the ways we currently use them.
13.
by redbad 13y ago
import ( "./utils" This is what's known as a relative import, and it's very bad. You want "github.com/johnnye/short/utils", or (better yet) put your base62 stuff in package ma
14.
by redbad 13y ago
Guarding your library boundary with a recover doesn't absolve your library internals from being nonidiomatic by using panics. (That the stdlib uses panic/recover in a few specific places does not make it broadly idiomatic.) Withou
15.
by redbad 13y ago
defer and recover have nothing to do with each other, except that in the few circumstances where it's appropriate to use recover, you often do it within a defer block. > are you saying that you don't need to handle except
16.
by redbad 13y ago
Note I said "as a matter of course". I agree it's useful in certain very limited circumstances, like parsing. But certainly not database work, unless you have a very different idea of what that entails than I do. Link to code
17.
by redbad 13y ago
No, you don't. You should never be using recover as a matter of course. You seem really hung-up on this point. Can you link to some code that illustrates your concerns?
18.
by redbad 13y ago
If you're recovering from panics, in general, you're doing something wrong.
19.
by redbad 13y ago
> it's incredibly hard to find a good engineer that knows > his stuff. They generally have PhDs and years of > training in math and whatever particular field they work > on. If you get one that is actu
20.
by redbad 13y ago
> Rust tasks have the same large fixed-size stack as OS > threads. A fine-grained concurrency model like a task > graph would be build on top of them. In the absence of other context (I don't really know mu
21.
by redbad 13y ago
> CSP and channels are meant for getting real (cpu > intensive) work done. You don't just use threads (or > greenthreads) "because concurrency". The whole point of green threads is that they'
22.
by redbad 13y ago
Those are both sub-problems.
23.
by redbad 13y ago
> Paste and match style (incredibly useful) is "alt-shift- > command-v" i.e. four keys . . . Four is too many. Three > is too many for such an important function. I've literally never heard of this
24.
by redbad 13y ago
> I don't take personal calls at my desk. My phone is on > silent at all times when at the office. If I need to > make a call, I step out. > > Even my desk phone is on silent. It sounds a single
25.
by redbad 13y ago
> there seems to be quite a few people suggesting that go > is the correct choice for every task. Literally nobody has said or implied anything like this.
26.
by redbad 13y ago
> Go's zoo of builtin data structures is really, really > poor compared to Java. This is a poor comparison because idiomatic Go typically doesn't use the `container` package.
27.
by redbad 13y ago
> And I believe I have explained what doesn't make sense > to me. You haven't explained those things, but rather attacked them.
28.
by redbad 13y ago
A mix of lint-y and style problems, and over-use of named returned parameters. https://github.com/cloudflare/bm/blob/master/src/bm/bm.go#L4... -- comment block should start with Dictionary. ht
29.
by redbad 13y ago
Frustratingly non-idiomatic Go code :(
30.
by redbad 13y ago
I'm not sure why you classify "a proper exception mechanism" as an "elephant in the room". Go will never have exceptions for control flow, and it's one of the best properties of the language.

More ›