enneff

166 ms·

1801.
by enneff 15y ago
Go strikes a nice balance, IMO. Value types (booleans, numbers, strings, structs, arrays) cannot be null, while reference types (pointers, slices, maps, channels) may be null. Also, Go calls null 'nil', which is fitting since nil is the zer
1802.
by enneff 15y ago
Yes.
1803.
by enneff 15y ago
The compiler is free to optimize this how it sees fit. Taking the address of a value doesn't necessarily move it to the heap.
1804.
by enneff 15y ago
There's no guesswork involved. The carriage return implies a semicolon. The rule is very simple and obvious in use (to me, the code you posted looks wrong - and it is). http://golang.org/doc/go_spec.html#Semicolons
1805.
by enneff 15y ago
Go doesn't define "lvalues," in the spec, but it does define "addressability." My comment would be more accurate if I had said "Go lets you take the address of any value in memory." (stack or heap)
1806.
by enneff 15y ago
Go allows you to take the address of any value. You just can't do pointer arithmetic like you can in C. That is, you can't address uninitialized memory.
1807.
by enneff 15y ago
http://www.urbandictionary.com/define.php?term=hero%20image
1808.
by enneff 15y ago
Not to my knowledge. It doesn't make much sense.
1809.
by enneff 15y ago
Actually, I think it does. OS X is a horrendous frankenstein of several different systems with different design philosophies. It is really, truly awful. (Although it works - I'm using an OS X machine to type this now.) One of the great thin
1810.
by enneff 15y ago
It's a mess because there are several ways to do the same things, and no two things are done in the same way. It feels like any time I want to do something new in OS X I need to learn a new system of some kind. That is bad design. It should
1811.
by enneff 15y ago
'Rob Pike is one of the "original neckbeards" that worked on Unix' Do you know that 'neckbeard' is a slur? It refers to someone who tries to grow a beard but can only grow hair on below their jawline, which is typical of adolescents. FWIW,
1812.
by enneff 15y ago
Package fmt is used all the time. It makes sense that it should have a short name.
1813.
Learn Go from your web browser(blog.golang.org)
4 points by enneff 15y ago|0 comments
1814.
by enneff 15y ago
It really irks me to see leaked screenshots of internal tools.
1815.
by enneff 15y ago
You are too cynical. Anyone who produces and gives away free educational tools is alright in my book. (Unless they're propagandists for an antisocial cause, I suppose.)
1816.
The Go image/draw package(blog.golang.org)
7 points by enneff 15y ago|0 comments
1817.
by enneff 15y ago
Your conclusion is flawed. We got an order of magnitude improvement by making a naively-constructed program efficient, and it was easy. That's hardly an indictment of Go's garbage collector. Also, the Go GC is a parallel GC which will use a
1818.
by enneff 15y ago
It's really easy to write your own implementation of the Image interface. At the moment the majority cases are covered. I could see something like what you describe coming in the not-too-distant future, as we see how people are using the pa
1819.
The Go image package(blog.golang.org)
57 points by enneff 15y ago|5 comments
1820.
by enneff 15y ago
When making these analyses people tend to forget that Google is a company of thousands of engineers. If we can devote a bit of engineering time to building better environments, the benefits across the entire company are multiplicative. Woul
1821.
by enneff 15y ago
If that's what you were trying to demonstrate then you were pretty far off the mark. The two programs are far from equivalent, and your Go code is just bizarre. I think this statement of yours is quite revealing: "Your example is not the sa
1822.
by enneff 15y ago
I didn't want to get into a slinging match, but I take issue with all of your points. "Error codes are a poor substitutions for Exceptions" This is debatable. "Have to code around lack of generics" Some people complain about this, but in pr
1823.
by enneff 15y ago
Wow, way harsh. Those of us that actually use Go are pretty enamored with it.
1824.
by enneff 15y ago
Actually, Go is great for writing web apps. Just not on the client side.
1825.
The Laws of Reflection(blog.golang.org)
39 points by enneff 15y ago|1 comments
1826.
by enneff 15y ago
That makes sense. I didn't know that. Thanks.
1827.
by enneff 15y ago
But isn't this one of the selling points of node.js? From their site: "Node's goal is to provide an easy way to build scalable network programs. In the "hello world" web server example above, many client connections can be handled concurren
1828.
by enneff 15y ago
What leads you to these conclusions? I am curious because you have some very definite opinions about it, and they are quite different to what I have observed in my Yoga practise.
1829.
by enneff 15y ago
Yoga has a spiritual aspect but you're not paying a yoga instructor for spiritual guidance. You're paying to use their space, to be taught the sequence of postures, and to receive adjustments to better achieve the postures. Yoga teachers do
1830.
by enneff 15y ago
It should really be "Visual design secrets for software engineers." It's kinda irksome how graphic designers try to own the word "design." Design is a vital part of all engineering, software or otherwise.

More ›