Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dsymonds
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
211.
▲
by
dsymonds
13y ago
You can state in documentation what interfaces a type implements. It is not uncommon to do that. For instance, the os package could have written something like: // File represents an open file. // It implements the io.Reader, io.Wri
212.
▲
by
dsymonds
13y ago
Only if you had a method with that exact signature: taking a []byte argument and returning an int and an error. You'd have to stretch to have that happen by chance.
213.
▲
by
dsymonds
13y ago
It'll arrive in the next release or two.
214.
▲
by
dsymonds
13y ago
If spammers and service abusers went away, CAPTCHAs would go away. Service providers don't use CAPTCHAs for the giggles. And the bad guys are getting better with OCR (or using sweat shops) so CAPTCHAs need to get harder to read to keep enou
215.
▲
by
dsymonds
14y ago
Go 1.1 has a much better map implementation, with fast-paths for common key types such as strings.
216.
▲
by
dsymonds
14y ago
You aren't going to see any radical changes to the language in the 1.x series.
217.
▲
by
dsymonds
14y ago
Erlang is a very different paradigm of language. It's much easier for someone familiar with C++ or Java to learn Go than it would be to learn Erlang. Erlang has a great concurrency model, but it's fairly clumsy for writing procedural code o
218.
▲
by
dsymonds
14y ago
Go has a builtin function called panic, which is much more useful and well-defined. panic("simulated runtime error")
219.
▲
by
dsymonds
14y ago
It's "when it's finished", but you can expect it in the near future. Go 1.1 is strongly backward compatible. You can start working on a large project right now with Go 1.0.3 and it'll work just as correctly under Go 1.1.
220.
▲
by
dsymonds
14y ago
Re: size of int and uint. The size of these types have always been specified to be either 32 or 64 bits. The only change here is that 64-bit platforms will actually use that flexibility. The probably most important consequence is that now y
221.
▲
by
dsymonds
14y ago
Their "free" comics require me to give them credit card details? I don't think so.
222.
▲
by
dsymonds
14y ago
Rob's been trying to get people to understand the difference since the early 1990s (Alef, etc.). It's not something new, nor unique to Go. In fact Go is a response to the desire for concurrency; it's not that Go popped out of nothing and th
223.
▲
by
dsymonds
14y ago
Doesn't necessarily apply. Courts have ruled that the 4th amendment can be limiter or suspended in certain situations. http://boardingarea.com/blogs/flyingwithfish/2010/11/20/how-...
224.
▲
by
dsymonds
14y ago
Any named type. You can't stick a method on []string; you have to name it first, then add methods to its name (T or *T).
225.
▲
by
dsymonds
14y ago
There's nothing stopping you writing your own hash map that can be configured with a custom hash function. The builtin map is limited to types for which the language defines ==. It's a simplifying trade-off; I don't think "acceptable" versu
226.
▲
by
dsymonds
14y ago
The HandlerFunc type in net/http ( http://golang.org/pkg/net/http/#HandlerFunc ) does this.
227.
▲
by
dsymonds
14y ago
There's nothing stopping you from talking to other employees about salaries. It's a myth that is propagated by companies in order to keep you in the dark about what they are paying other people, to deprive you of information, and to keep yo
228.
▲
Corporate Hackathons: The Fine Line Between Engaging and Exploiting
(jamiemsmyth.blogspot.com.au)
2 points
by
dsymonds
14y ago
|
0 comments
229.
▲
by
dsymonds
14y ago
How is it hard to satisfy the rules that are being complained about here? It should be trivial to arrange for no sponsor logos, no sponsor speakers, and so on.
230.
▲
by
dsymonds
14y ago
The 27 year old developers probably only thought they were grizzled veterans.
231.
▲
by
dsymonds
14y ago
It's small, but quickly growing.
232.
▲
by
dsymonds
14y ago
I work with him at Google. Google has a single codebase shared by tens of thousands of engineers. People have areas of that that they own, but it is a wrong characterisation to say Rob "works in relative isolation from other programmers".
233.
▲
by
dsymonds
14y ago
Uh, no. Rob works with a number of other programmers on code that is directly used by thousands of other programmers.
234.
▲
by
dsymonds
14y ago
Why is it now trendy to publish private mail like this? Is there really that much public benefit to be had?
235.
▲
by
dsymonds
14y ago
Because tracking memory allocation and ownership in a concurrent program is very hard. Programmers have to track a lot of that stuff in their heads, and it's easy to make mistakes. If the language is garbage collected, however, the programm
236.
▲
by
dsymonds
14y ago
You are spouting nonsense sprinkled with vague half-truths. You have a distorted view of what one part of Google might have been like for the short time you were there. There is no forced curve. One of your "Perfolympics" is actually option
237.
▲
by
dsymonds
14y ago
Nah, he doesn't strike me as pretentious enough. ;-)
238.
▲
by
dsymonds
14y ago
There's other options than "release early release often" and "waterfall".
239.
▲
by
dsymonds
14y ago
A new programmer is a bad programmer. There's no shame in that. In fact it's better for a new programmer to realise that; the worst programmers are those that don't even realise they are bad. A new programmer may still be learning, but th
240.
▲
by
dsymonds
14y ago
The big problem with errno is that it's a global: there's exactly one of them for your program. As soon as you start using threads you are screwed. Go aims to make concurrency right. That means you can depend on a global variable for propag
More ›