HN user

tuxcanfly

78 karma
Posts2
Comments22
View on HN
Laplace’s Demon 12 years ago

So instead of having only two options, or a third invisible option, there is only one real option and the demon cannot be wrong or it cannot be right.

This third neither right nor wrong option reminds me of 'Mu' found in eastern philosophy and highlighted in Hofstadter's GEB and it forms another crucial part of self-reference and recursion as mentioned earlier in your comment.

Is there a chance ty or a similar implementation will make it into Go core? What do you think about Go designers being generally averse to the idea of parametric polymorphism?

“One must lie low, no matter how much it went against the grain, and try to understand that this great organization remained, so to speak, in a state of delicate balance, and that if someone took it upon himself to alter the dispositions of things around him, he ran the risk of losing his footing and falling to destruction, while the organization would simply right itself by some compensating reaction in another part of its machinery – since everything interlocked – and remain unchanged, unless, indeed, which was very probable, it became still more rigid, more vigilant, severer, and more ruthless.”

― Franz Kafka, The Trial

> “Those DVCS kids, they got just what they deserved, won’t it be great when we can get back to a real VCS like Perforce”.

This entire article is based on the false dichotomy that either we use get along with github as it is or go back to svn.

Given the number of projects which directly pull code from github and execute it on production machines, it is not unreasonable to expect basic security from a hosting provider. I don't see why github should be given a second chance.

But don't the alternatives also depend on list slicing? Heck, the title is `coping a list`. If you have a different datatype, it is the business of that type to specify how to copy using __copy__, isn't it?