Unrealistic security should be the only reason to disapprove of a bitcoin ETF governed by the SEC. Not only is it poorly suited for reckless centralization by thousands of indirect investors, but bitcoin as a whole would be setup up for massive government retaliation once the keys are compromised. MtGox x 10,000.

Good move. I've been looking for a security-focused registrar. Will CloudFlare Registrar open its doors outside of an Enterprise plan?

I'd be surprised if they did. No way it can be economical to do this at scale for normal domain reg costs.

I'd be surprised if they didn't. There's a markup at which it'd be very economical to be a broader registrar. Future upselling is worth pulling users away from other registrars. Some of them will compete against CloudFlare sooner or later. Google's headed that way.

1. I don't see how.

2. Impure?

3. That's the point. It's to force people to stop using maps as if they're sorted.

4. Why would you want to rely on the arbitrary nature of a hash table for order?

5. That's the best type of boilerplate. It's short. It brings clarity. You might not need custom sort functions. The sort package supports basic types, which you'd use if you're keeping track of an index with []int for instance. https://golang.org/pkg/sort/

It's not about relying on hash tables for order. It's about the invariant that traversing a hash table N times will produce the same ordering each time, as long as the hash table is not mutated, even though that ordering is unpredictable.

Disclaimer: I've never used this feature myself and I sympathize with the desire on the part of the Go designers to avoid accidental de facto stabilization of hash table iteration order--though it sounds like it could have been done without drawbacks by randomizing at process start.

It is to prevent hash tables being relied on for order. Randomization was added so maps aren't treated as invariant. The behavior in a range of a map is no less correct to be changing (in Go) rather than unchanging (in other languages). In other words, invariant relative to what? It's not too important. It's one of numerous ways Go promotes clearer design, at least in my eyes, to have disorder represent unordered and order represent ordered.

This is a very philosophical comment, but I'm not seeing a specific, practical advantage that randomizing on every iteration confers over randomizing on process start.

Can you provide one? (I'm genuinely curious.)

It's no more philosophical than saying the alternative is proper. Uniformity of expectations seems more practical to me. In contrast, I wouldn't see an advantage in map ranges ever staying the same even per process. There's no reason to promote that reliance.

Well I gave 5 reasons up at the top :)

But from a philosophical perspective, referential transparency is a big one. We should prefer to make functions referentially transparent, because it makes them easier to reason about. Sometimes we do not, because it would be too slow or too awkward. But in this case, the loss is gratuitous.

Or to put it concretely: in Python (and every other language), we have the fact that `dict.keys() == dict.keys()`. In Go, this is true sometimes. Doesn't that seem weird to you?

But there is one, which the original post in the thread described: you could for example convert a map of arrays to a flat array by iterating over it repeatedly and printing the ith element of each array. This doesn't work if every loop over the elements gets a different ordering.

You can mimic that syntax in Go. I don't recommend it but you'd only have to add a function.

    func it(n int) []struct{} {
        return make([]struct{}, n)
    }

    // ex. 1:
    for range it(10) { 
        fmt.Println(".")
    }

    // ex. 2:
    for i := range it(10) { 
        fmt.Println(i) 
    }

I can't think of any modern non-monopoly companies that have obtained global domination without a need to perpetually acquire niche competitors along the way. That's especially so as several companies (Netflix, Amazon, Apple, Google, and non-US players at large) vie for limited attention.

Do you know what means the word "Niche" in France : it's a house for dogs, literally, http://www.jardiland.com/mes-animaux/12431-chiens/12432-habi...

We, Afrostream, have a bigger house to fill ;)

Rob Pike's Ivy: https://github.com/robpike/ivy

Video about it (Nov 2014): "Implementing a bignum calculator" https://www.youtube.com/watch?v=PXoG0WX0r_E

I left it on overnight once. It worked. The pixel re-stuck several times after so it took a few more sessions. It's been normal going on a few years. You might try rubbing the pixel area a bit and testing other stuck pixel fixing software.

Days convey immediacy and scale. "Today" and "same day" balance precision. If time between an exploit becoming known and fixed consistently happened in 100 seconds or less, 0-sec might sound ok. Come to think of it, 0-sec is a fitting pun.

"0-sec" isn't too bad, but the plural can make for awkward conversation.

0-sec is a terrible name if you're working in sec...

Hell.com was in a league of its own in this genre. Those were the days. It's fittingly tragic that it's now reduced to a landing page of ads.

Wow, it sure was. Did anyone expose what it was actually all about, since it claimed to have a membership site or something?

Ah the days of entering in random URLs and seeing what happened...

I was a member, bought back my soul, and had a hell.com email address for years. As aric said, it was a cabal of artists and designers, mostly using Flash. There were discussion boards, spaces to explore, and so on.

The associated site http://www.cygne-noir.com/ is still up, but with just an image. There's probably a login somewhere, but you must know the URL. And http://final.org/ is for sale. But http://www.8081.com/home/ and http://www.medialounge.org/ are still there, and seem much as I recall.

Exploring past those gates into membership is rumored to have led to a cabal of artists and designers in the web's avant-garde scene. We may remember hell.com for what it represented. It was a rabbit hole that unsettled minds, unfurling beyond depths of a web people previously thought they knew, to cause wonder.

It's hell.com. Seems highly appropriate.

If you wanted to do that:

   b := &a
   fmt.Println((*b)[0])