convulsive

>4. Program authors are forced to explicitly document ahead of time all situations in which their program code might be modified in the future

Can you point me to a resource that explains this in more detail? I think I've gotten the gist of how Ethereum works, and have gone through a tutorial of Solidity, but I'm unclear how versioning will work in Ethereum (even though I do have some guesses for how it could be implemented).

How would I deploy a new version of my contract? Would I have to implement a mechanism for basically hot loading new code?

>Now, go ahead and name some non-gaming uses of CV1. I bet you can't come up with anything compelling

False. I own a DK2, which I regularly show to other non-gamers. It always blows their mind and they immediately start considering possible applications in their fields (film, medicine, architecture, dataviz, installation art, etc). I've even gotten people to introduce it to their coworkers and bosses to consider using it in some capacity.

Don't worry. If HN hates it, it's probably going to be important. :)

Hi, can I shoot you a few quick questions over email about the process of applying for OPT extension while employed at your own company? Would really appreciate some advice on this.

nevermind, i completely misread your comment

you're claiming that if if it was meant to be a critique it's ineffective yet you found yourself realizing "how much [you were] thinking about this silly little thing"

interesting!

"The discovery of the alphabet will create forgetfulness in the learner’s souls, because they will not use their memories; they will trust to the external written characters and not remember of themselves. You give your disciples not truth but only the semblance of truth; they will be heroes of many things, and will have learned nothing; they will appear to be omniscient and will generally know nothing." -- Socrates, in Plato's "Phaedrus"

This is not the 'evolutionary perspective' as you claim it is. This is just your perspective dressed in evolutionary terminology so that the reader will believe that if you accept human evolution, you MUST accept this conclusion. But the fact that you came up with a possible evolutionary past and thought of a constraint that could've pushed us to develop the adaptive behavior of procrastination doesn't in any way imply that this is actually the way things happened. Procrastination might've been a fitness-maximizing adaptation (or even just a spandrel [1]) for so many other equally convincing reasons.

It's really strange that while for molecular & morphological phenotypes we use rigorous methods to measure evolutionary relatedness so we can determine possible sequences of evolutionary adaptations that led to them, when it comes to behavioral phenotypes people think that conceivability arguments coupled with very inconclusive evidence are sufficient to demonstrate that some evolutionary story is true.

[1] http://en.wikipedia.org/wiki/Spandrel_(biology)