397 karma · joined October 24, 2010
I was reading "A Deepness in the Sky" by Vernor Vinge the other day, and his portrayal of that was pretty good. Basically on a long trip the crew cycles being awake and "on watch". So there are always some people awake to deal with problems, but everyone only has to expend a year or two of their lifespan on the trip. (As an aside, great book)
Awesome.
How do you feel about derby? (http://github.com/codeparty/derby)
Edit: That probably came across more snarky than I intended. The point was that this is easily said, but hard to do right.
Or a Coffee-Maker... Instant factory pattern.
POST /booking/:id/cancellation
Because you are creating a 'cancellation object' belonging to that booking.Ninja Edit: Really it is about being consistent, and predictable, so that people using your API can guess how it will act. If you are using an API of yours, and can't guess what the correct url/method is, you should change the API. (I forget who said that)
Or faster rockets.
You'd love Hyperarchy (http://blog.hyperarchy.com/2011/07/19/hyperarchy-democracy-f...)
Nice idea!
> It's not like they make anything that can be infringed on.
Or, require the patent holder to prove 'damages'. Since they don't make anything and don't actually use their patents there are no damages lost.
I hope you can turn that off!
Edit: Just discovered the associated playlist chat-room.. nevermind.
"It turns out that, in Go, you can't write a self-recursive anonymous function - there's no way to make it refer to itself. Well, you can do a dirty hack that's the "official work-around" (I'll let you google for the bug report)."
To summarize this argument: 1. It is impossible to have a self-recursive anonymous function in Go. 2. Oh wait.. It is completely possible, but far too ugly to soil this blog post.
I looked up the temporary solution (http://code.google.com/p/go/issues/detail?id=226). It is this:
var recurse func()
recurse = func() {
recurse()
}
The proposed permanent solution is allowing recursive function definitions, because that is the proper solution instead of adding a magic self keyword like other languages do.(tl;dr The author just doesn't like the fairly-simple work-around proposed while the language is still developing)
Edit: There definitely are far more important things in Go I dislike, and would change, however this blog post is essentially fluff.
It's very kind of you to offer to make more space for the rest of us. You're welcome to refuse/object-to life extension on moral grounds. Somehow, though, when push comes to shove, I don't think you would.