HNHacker News
TopNewBestAskShowJobs

nyan_sandwich

200 karma · joined August 24, 2012

Mechanical engineer, programmer, and aspiring entrepreneur based in Vancouver, BC.

I'm currently interested in making technical knowledge and thinking more accessible and convenient, and fixing Science in general.

submissionscomments
nyan_sandwich··on Another go at the Next Big Language
everything is package prefixed, names are long.

Totally minor, but reminded me of my days with java

nyan_sandwich··on Ask HN: What is your ideal income?
I'm near-broke and unemployed.

I can live on <$10k/yr (maybe as low as $6k)

I imagine myself with $10k being comfortable.

If I get a job (working on it), I'd expect $40k for 2013, would not be too suprised at $60 for some crazy tar-sands job. (I'm a mechanical engineer, and/or programmer).

Supporting myself in Vancouver, BC.

I want more. There is no enough. All money over $10k will go to charity. At least that's the ambition.

nyan_sandwich··on Another go at the Next Big Language
I was really excited about Go. Designed by some gurus, seemed to get everything right, google app engine supported it.

Then I tried to build something.

Java-like verbosity. Meh, I can deal with it.

[]byte and string aren't the same. Whatever, a few extra lines and thot cycles here and there, no big deal.

Overly complex library functions. Let me explain this one. In Lua, markdown (discount) is a single function. In Go, there was a bunch of extra stuff that just seemed like noise. Likewise for cypto, Base64, stringwriters, bunch of other stuff.

A bunch of little annoying stuff like that adds up. Eventually I just said fuck it. Maybe I'm not hardcore enough or something, but now I'm back with LuaJIT.

Goroutines are cool, tho. Lua's synchronous threads aren't quite the same. Also google's app engine datastore is sweet. Nice and simple, no screwing around with SQL. If I had to do systems stuff, I'd reach for Go.

LuaJIT is faster anyways.

nyan_sandwich··on Go's unique approach to OO
It doesn't get a pointer to the struct, it gets an object that implements whatever interface. At least that's the story from the type system perspective.

Given that, it seems easy enough to just pass a {pointer, vtable} value.

In C++ (if I understand correctly) each object/class has one vtable. In Go, it seems that each type has as many vtables as are needed for the contexts it's called in.

See also type classes in haskell.

(this is all guessing. Someone please call me out if I'm wrong)

nyan_sandwich··on The Worst Argument In The World
Actually it's kindof taboo on LW, hence the apology.

Thinking straight about politics is hard, so it's not a good practice case.

"learn programming by writing an industrial-quality OS"

nyan_sandwich··on How Long Do You Want to Live?
First reaction: What kind of stupid question is that? I want to live as long as possible.

Having read the article: less than 1% share my view. Yikes.

I think for most people, questions like this are what I'd call a "philosophy landmine"; say certain things and it causes people to stop thinking and repeat some standard cultural tropes or go spinning off into faux-philosophy-land.

Kind of depressing.

nyan_sandwich··on Your Brain Can Be Hacked
Sure it's equivalent to brute force now, but it's not like the brain is doing a cryptographic hash. I would not be suprised if a bit more development made it possible to break passwords one character at a time or something on that order of complexity.
nyan_sandwich··on Why Self-Track? The Possibility of Hard-to-Explain Change
It looks like I have to sign up to play. Trivial inconvenience, I know, but now I'm bored and doing other things. Just FYI.
← PreviousPage 3 of 3