dsymonds

12 ms·

91.
by dsymonds 12y ago
The government most likely paid the other two thirds via PBS.
92.
by dsymonds 12y ago
That's been proposed, but it won't happen. There's too many edge cases, and it only works on the Go compiler because it has a particularly constrained style and rsc can make the relevant hacks as a one-off effort.
93.
by dsymonds 12y ago
It's a shame the author mixes up UTF-16 and UCS-2 when he says "Because it turns out UTF-16, another very popular encoding scheme, can’t represent codepoints that big." in reference to 0x1FFFFF.
94.
by dsymonds 12y ago
"stable" here means zero population growth over the long term, which actually requires a little above 2 per couple to account for people who die before being old enough to parent children. 2.1 is the common approximation for that.
95.
by dsymonds 12y ago
It's a big deal, but it's not exactly news. It was part of the Go 1.4 release, about a month ago, and also announced well before that on the golang-dev mailing list. Both times it was discussed extensively here on Hacker News too.
96.
by dsymonds 12y ago
The Go compiler in 2007 was written in C because it was an adaptation of the Plan 9 C compiler. That was done because it was the expedient choice at the time, especially while the language was still being designed and would change quite a l
97.
by dsymonds 12y ago
That's true. It still means there's hundreds of folk who qualified for the NBA at all, and thousands in the next level down, and all those are much much better than the local sports club players.
98.
by dsymonds 12y ago
And digging is much more expensive to do initially (think two or three orders of magnitude), though it's often cheaper in the long run due to less maintenance and repairs.
99.
by dsymonds 12y ago
The protobuf code is a concrete instance of a code generator. `go generate` is a general mechanism for triggering a code generator. They are complementary, and you could imagine the former using the latter.
100.
by dsymonds 12y ago
Why does it upset you that it comes baked in? If you don't care for it, don't use it. It's for package authors, so you won't be exposed to it unless you want to.
101.
by dsymonds 12y ago
I'm not trying to brush off concerns. They're fair, but I don't think it's particularly fatal. If you're using stringer, you've opted into it by adding //go:generate lines to your source, and so if yo
102.
by dsymonds 12y ago
Well, it's more than just dependencies. `go generate` isn't meant to be involved at all if you're just building a package or command for using it, which is quite a bit different to `make`.
103.
by dsymonds 12y ago
`go generate` is deliberately not integrated with the other commands because it should not be used for things that are necessary when you just want to use a package. We don't want to force people to have to install random development
104.
by dsymonds 12y ago
It's true that it's more general, but the name is chosen to indicate what its intended use is, namely generating code.
105.
by dsymonds 12y ago
`go generate` is not at all like `make`. I don't think you read the article carefully enough.
106.
by dsymonds 12y ago
It doesn't really happen all that often in practice, and when you're hacking on a package that relies on this it's easy enough to have `go generate && go test` sitting in your shell history for that iteration cycle.
107.
by dsymonds 12y ago
Yes, but he wasn't trying to compute numbers. He was trying to build a calculator. There's a difference.
108.
by dsymonds 12y ago
One use case would be to exhaust a channel (that is, read everything off it until it is closed). Another might be to loop over something of a fixed size to correlate with a corresponding number of other things.
109.
by dsymonds 12y ago
Have you actually observed the Go community and how Go has been developed over the last five years? What you are saying are fair concerns in the abstract, but I cannot reconcile them with the reality of how the Go project operates. You also
110.
by dsymonds 12y ago
Because we want a good code review system, and GitHub doesn't have that. More discussion: https://news.ycombinator.com/item?id=8715529 https://news.ycombinator.com/item?id=8605204
111.
by dsymonds 12y ago
It will be soon. I'm working on it.
112.
by dsymonds 12y ago
It didn't make it in, but there's no real strong moves for it to be in the standard library anyway. It works well enough in a go-gettable package.
113.
by dsymonds 12y ago
It's been a very active open source project for over five years. It's roughly 5 issues per week.
114.
by dsymonds 12y ago
You could file a bug against GitHub. Maybe they could also fix their recognition of email addresses to permit `<research!bwk>` too.
115.
by dsymonds 12y ago
See https://help.github.com/articles/why-are-my-contributions-no... . The most likely reasons are: - your email address used for your Go contribution is not associated with your GitHub account - your contribution
116.
by dsymonds 12y ago
Unfortunately a significant problem was just found in the process for migrating the issues from code.google.com to GitHub. We're going to re-do the migration, but need to lock down the repo so we don't blow away anything that some
117.
by dsymonds 12y ago
This was announced in mid November: https://groups.google.com/d/topic/golang-dev/sckirqOWepg/dis... To be clear, Go is not "on" GitHub except for its issue tracker and wiki. The code is being d
118.
by dsymonds 12y ago
GitHub is only a mirror. The real work is happening on go.googlesource.com. https://groups.google.com/d/topic/golang-dev/sckirqOWepg/dis...
119.
by dsymonds 12y ago
I don't think zaphar was targeting you specifically.
120.
by dsymonds 12y ago
It's not presumptuous if that's what almost every HN comment section on an article about Go devolves into.

More ›