dsymonds

Humanity made no meaningful progress in getting "to the stars" for thousands of years too, then in the space of a few decades we did.

It's usually done in bulk, so the overall payoff is the combination of value and number of targets, but the effort is typically sublinear with the targets. Something easier to attack but relatively low in number is not as juicy as something a bit harder (where the effort is mostly a one-off up-front rather than per target) but having many, many more targets.

and 90s versions like Me No Fry (https://www.youtube.com/watch?v=rsgdT8YYwJo)

It's low with CPR alone, but getting an AED involved (which should be accessible in most urban places these days) raises the chances to 50-70%.

It's because units up to hours are of a fixed size, but days in most places are only 24h for ~363/365 days of the year, with some being 23h and some being 25h.

(This is ignoring leap seconds, since the trend is to smear those rather than surface them to userspace.)

If the author reads this, you have a misspelling of "diaspora" in the first sentence.

The map iteration order was always "random", but imperfectly so prior to Go 1.3. From memory, it picked a random initial bucket, but then always iterated over that bucket in order, so small maps (e.g. only a handful of elements) actually got deterministic iteration order. We fixed that in Go 1.3, but it broke a huge number of tests across Google that had inadvertently depended on that quirk; I spent quite a few weeks fixing tests before we could roll out Go 1.3 inside Google. I imagine there was quite a few broken tests on the outside too, but the benefit was deemed big enough to tolerate that.

Did you read Part 2, linked from the bottom? It has plenty of technical details.

Not a typo.

http://www.tom-yam.or.jp/2238/src/slp.c.html#line2238

It's what we'd use `&=` for nowadays. Note that the "B" language had these sorts of operators around the opposite way for how they appeared in "C" (e.g. read https://www.bell-labs.com/usr/dmr/www/kbman.html).

That's exactly what the Lions' book is.

Yeah, there's been a few plans announced:

https://blog.golang.org/go2-here-we-come

https://blog.golang.org/go2draft

https://blog.golang.org/go2-next-steps

It doesn't have to be a handshake and a nod. Things can still be clearly written down. But formal contracts with consequences take it up a notch. And this isn't about how you "conduct business"; that's a very business-oriented view of what's going on.

An NDA is a legal agreement. It's entirely possible to organise coordinated disclosures without a legal agreement. The folks pushing NDAs, however, don't seem to be interested in other sorts of agreements.

One big reason for shutdown rules with home PV systems is to keep firefighters safe. If your house is on fire, the firefighters really don't want to be contending with high voltage electricity as well.

They likely can't, but they can fine EPAG, which is a German domain registrar. The matter at hand is that ICANN was trying to allegedly force EPAG to violate GDPR.

> To search for anything about Go in your search engine of choice use the word golang rather than go when searching. For example to search for how to open a file I would search for golang open file.

This seems to be a recurring chestnut, but I would have expected the author to actually test it. If I search for [go open file], 8 of the first 10 results on Google show useful information.

Even then, I think it'd be unlikely that the time-cost wouldn't make it worthwhile. People generally underestimate how much time gets soaked up by managing a computer service.

Are you sure you fully understand the benefit?

$35 is, what, 30 minutes of an engineer's time from a company's perspective? If the management of the service would take any more than that every month (and it easily could!), you're ahead.

context.Context is an interface because it is known there are multiple implementers (several in the context package itself). The sql driver.Value is actually the other way around: the sql package is the consuming package (for the driver).

That's true, but the standard library also has strictures about backward compatibility that have ossified some bad choices. The crypto examples you give are arguably exactly this; even the later ones are probably a mistake, but are at least consistent with what can't be changed.

A redback bite generally requires medical attention; though not triple-0 level urgency, it shouldn't be a wait-and-see-how-you-feel treatment.

Did you actually read the article? It is clear from the background and history sections that the need for versioning was apparent from early on.

Good to see rustfmt arrive.

Sad that it is configurable, though. The biggest benefit of its predecessors such as gofmt is that they are not configurable, leading to a much more uniform formatting style and avoiding endless discussions about whitespace layout.

In this context, USO means Universal Service Obligations, namely that approximately everyone can get access.

https://www.acma.gov.au/Industry/Telco/Carriers-and-service-...

No, that's not the definition of theft.

Theft is the criminal (i.e. against the law) stealing of someone's property without their permission. This situation would have been complying with the law, stupid as it may be. It's much closer to abandoned property or salvage.

Seems broken. It doesn't implement a proper regular expression engine.

http://regexr.com/3f8ge

c.f. https://swtch.com/~rsc/regexp/regexp1.html

Doesn't Patreon fit this already?

e.g. for one random example: https://www.patreon.com/monkey2

Your maths seems off. 600 years at, say, 25 years per generation, yields 24 generations. Doubling each generation gives a factor of 2^24, or around 16 million, not 1 billion.

Bah, the HN markup dropped my asterisks in those types.