bradfitz

31 ms·

331.
by bradfitz 8y ago
> The English language is defined by it's usage Speaking of which: I've been anxiously awaiting the day when dictionaries finally give up and declare "it's" as a valid spelling of "its".
332.
by bradfitz 8y ago
I agree, but there's not much, and it's usually for decent reasons: * the "time" package hooks into the Go scheduler. * the "reflect" package needs type information out of the runtime. * the "net" pac
333.
by bradfitz 8y ago
One of the main motivations for adding generics is that we could then put typesafe algorithms and data structures in the standard library.
334.
by bradfitz 8y ago
Whoops, thanks. Fixed.
335.
by bradfitz 8y ago
Lack of generics was never part of "Go idealism". It has remained an open question for 9 years. It was added to the FAQ in 2010: https://web.archive.org/web/20101123010932/http://golang.org...
336.
by bradfitz 8y ago
Is it an explicit design requirement that we never invalidate any Go 1 code or bifurcate the community. Any language changes must keep that in mind. Also, "Go 2" won't be a release as much as it'll be a series of release
337.
by bradfitz 8y ago
Nope, sorry. I guess you can read it from home or on your phone if you employer doesn't trust you. :)
338.
by bradfitz 8y ago
Of possible interest, I gave a talk about "Go 1.11 & Beyond" (read: "Go 2") a couple weeks ago: https://docs.google.com/presentation/d/1EwuJhEHR5Trr2aXBPQaj... (See speaker notes for more c
339.
by bradfitz 8y ago
Generally faster. https://golang.org/doc/go1.11#performance Depends what you measure. Some parts if you microbenchmark them are 10x faster, or much more.
340.
by bradfitz 8y ago
It grows but not super fast. Like the other comment said, once you include the runtime and Unicode tables, that's a fair bit of it.
341.
by bradfitz 8y ago
init-time load has become a pet project of mine lately: https://github.com/golang/go/issues/26775 A new person on the compiler might be working on that too as a warm-up task.
342.
by bradfitz 8y ago
One of the other exciting things in this release is the almost entirely rewritten "prove" pass in the compiler: https://golang.org/doc/go1.11#performance-compiler > The compiler now performs significantly
343.
by bradfitz 8y ago
And this is temporary. In the future we should be able to both do better size-wise & also to generate multiple WebAssembly output modules, perhaps one per Go package, to enable better (more fine-grained) caching.
344.
by bradfitz 8y ago
I suspect if we knew we'd just measure it ourselves rather than measuring animal movement from space?
345.
by bradfitz 8y ago
Lutron devices don't form a mesh network, though? And a limit of only one range extender. And only 50 devices? http://www.casetawireless.com/Pages/faqs.aspx I'll stick with Z-Wave, even though it's not p
346.
by bradfitz 8y ago
The Go linker does dead code elimination already.
347.
by bradfitz 8y ago
Release notes: https://tip.golang.org/doc/go1.11
348.
by bradfitz 8y ago
Could be worse. I probably wouldn't be doing this in, say, Hawaii.
349.
by bradfitz 8y ago
OP here. I mirror all my data to Amazon S3 and Google Cloud Storage too. Or rather, Perkeep ( https://perkeep.org ) does this for me.
350.
by bradfitz 8y ago
That's pretty vague. A server (no details) didn't work as well as hardware (no details). Lot of missing info there.
351.
by bradfitz 8y ago
It was 55 dB a meter in front last time I checked, before the new rack which if anything made it a tad bit quieter. It's in my garage, though, so I don't care. But it's not annoyingly loud. I used to have a 1U server in this
352.
by bradfitz 8y ago
Much of this exercise was me playing with Ceph, which is pretty impressive. Having VMs float around with shared storage makes complexity elsewhere go away. i.e. I don't need to deal with CARP, VRRP, etc.
353.
by bradfitz 8y ago
That's Washington's average. The actual rate is 5-6 cents or so for the first block, and then 15 cents after some amount.
354.
My home lab setup for highly-available Internet(github.com)
699 points by bradfitz 8y ago|287 comments
355.
by bradfitz 8y ago
If something got slower, file a bug with details. We look into all such reports.
356.
by bradfitz 8y ago
See https://news.ycombinator.com/item?id=17297472 elsewhere in this thread for why.
357.
by bradfitz 8y ago
https://twitter.com/tallclair/status/991621542265180161 -- "Google has been relying on gVisor to sandbox production workloads for years. I'm super excited that we've open sourced! Now we can talk ab
358.
by bradfitz 9y ago
Go just got native support for private blockchains today: https://twitter.com/bradfitz/status/980332627159744512 ( https://go-review.googlesource.com/c/go/+/103862 )
359.
by bradfitz 9y ago
> Inserting yield points judiciously in loops isn't that incredibly difficult, and neither is reducing the cost of a yield point. The Go team has done both over the past few years but we haven't been happy enough with the perfo
360.
by bradfitz 9y ago
Ah, sorry, I didn't realize you were linking to a comment. I read that was a link to Cargo itself.

More ›