Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dsymonds
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
dsymonds
11y ago
There's also a Go port of S2: http://godoc.org/github.com/golang/geo/s2
62.
▲
by
dsymonds
11y ago
No, goroutines are never cleaned up until they exit. If they are blocked on a channel that no-one else references then they'll be blocked forever.
63.
▲
by
dsymonds
11y ago
So it's not "restricted to 100 mails per day". It's limited to 20,000 per day, and that's only until you sign up for support.
64.
▲
by
dsymonds
11y ago
Email is only limited to 100/day for free apps. https://cloud.google.com/appengine/docs/quotas#Mail
65.
▲
by
dsymonds
11y ago
Yep, the link should be https://golang.org/dl/ . Work is ongoing to make golang.org be HTTPS only.
66.
▲
by
dsymonds
11y ago
It means there's an oversupply of people who want engineering jobs. Most people applying for software engineering positions aren't able to program even the most basic of things. That doesn't mean there's too many qualifi
67.
▲
by
dsymonds
11y ago
That wasn't what I was replying to. aaggarwal was asking how easy it was to move to it. I was saying that it's easy. If you find it too primitive, well, that's a fair opinion, but it's still easy to move to. I think it&#
68.
▲
by
dsymonds
11y ago
Maybe it's just that Python/Ruby programmers are more inclined to publicly discuss their switching?
69.
▲
by
dsymonds
11y ago
Yeah, C is probably the hardest to learn in that set.
70.
▲
by
dsymonds
11y ago
Any decent programmer should be able to switch between {C,Java,Go,Python} without too much difficulty. They each have their own differences and learning curve, but as long as a programmer doesn't identify themselves too tightly as a sp
71.
▲
by
dsymonds
11y ago
It's not hard to find people switching from Java to Go (e.g. http://www.infoworld.com/article/2608571/application-develop... , which I found within 10 seconds of searching). It's true that Go doesn't
72.
▲
by
dsymonds
11y ago
I think it can help with that in the sense that Go packages don't have complex boundaries and the type system is simple and self-contained. You don't have to trace an inheritance hierarchy to understand any given type, so a projec
73.
▲
by
dsymonds
11y ago
go get google.golang.org/cloud/bigtable
74.
▲
Google Cloud Bigtable
(cloud.google.com)
16 points
by
dsymonds
11y ago
|
2 comments
75.
▲
by
dsymonds
12y ago
That's not true at all.
76.
▲
by
dsymonds
12y ago
FYI, if you don't need required/optional, non-zero defaults and extensions, try `syntax = "proto3"`. It generates much better Go code.
77.
▲
by
dsymonds
12y ago
gRPC is based on the internal Stubby RPC system, and that works over HTTP/1.1 based on CONNECT and switching to raw TCP. That works well enough, but the HTTP/2 goodies are too good to pass up.
78.
▲
by
dsymonds
12y ago
Streaming RPCs in both directions (client to server, and server to client) is one big feature. It's not really possible to do client-side streaming with HTTP/1.1, especially if you have proxies in the way. Independently framed mes
79.
▲
by
dsymonds
12y ago
Thanks. That's good data. I haven't seen any measurements for a few years. It's good to see that gccgo has caught up. Which version of gc did you test? Yes, the release schedule is another important reason for building our ow
80.
▲
by
dsymonds
12y ago
Yes, that's why there's both gc and gccgo (llgo came later). Apart from the rigour of having two independent compilers, they are seeking different tradeoffs. gc is very interested in running fast, and gccgo benefits from decades o
81.
▲
by
dsymonds
12y ago
What's your counter-proposal? If you're building a new language, you need a new AST. You can't represent Go source code in a C++ AST. There are alternate compilers for Go, in the form of gccgo and llgo. But those are both v
82.
▲
by
dsymonds
12y ago
In source control, yes. There's not yet a stable release where that's the case though; Go 1.5 (due later this year) will be that release.
83.
▲
by
dsymonds
12y ago
Future versions will still be built with any current published compiler. There are binary releases for each major release, and it's not hard to avoid using new language features in the compiler, so building from source only requires th
84.
▲
by
dsymonds
12y ago
Obligatory comment about how if you can't match it in linear time then it's not a regular expression.
85.
▲
by
dsymonds
12y ago
I don't think it's true that "Googlers generally don't like Go". Some like it, and some don't. From my vantage point, the majority (maybe 80% or so) who have actually tried to do real with in Go seem to like it
86.
▲
by
dsymonds
12y ago
No-one said "disturbing". It's weird if you've come from an environment where you do your individual work in private, and only show it to people when it's ready to be committed/merged. No-one said that that poi
87.
▲
by
dsymonds
12y ago
We expect contributors to sync and run all the tests. The public forking is the weird and unnecessary part. Gerrit is the alternative used, and contributors have a full local clone of the git repo, with their commit, and that's priva
88.
▲
by
dsymonds
12y ago
I think you mean s/researching/adopting/, since you are only referring to the outcome, not the study or decision making that arrived at the outcome. The Go team generally knows about modern things; we deliberately choose not
89.
▲
by
dsymonds
12y ago
And Gearman.
90.
▲
by
dsymonds
12y ago
You said "It's a bit juvenile to blame building codes without also admitting why we have them: they save lives."; namely, for safety reasons. yummyfajitas pointed out that safety has nothing to do with the issue at hand. Your
More ›