As an uninformed observer, the studies were the least “convincing” part of his argument. It was the minimum force transfer numbers and the human force limit numbers, and then the note that other sports have stricter standards for the protectiveness of their gear that was the standout argument.
The obvious questions that come to mind are “does commonly available gear exceed the standards despite the minimums” and “is the test representative of real world impacts”.
75MB/5 sec benchmark results (using internal AWS network to pull from S3!) sound dubious. You can get 4Gbps+ down from S3 within the same region in my experience, that's 30x faster than these numbers.
I've built this page since I often just want to pick a spot instance type that gives me biggest bang for the buck. Amazon's own pricing page is still very confusing, and ec2instances.info is great but it is a static website and adding spot prices there is nontrivial.
I've also fixed a few minor things that annoyed me, such as correct sorting by instance type (so that r3.16x goes after r3.4x) and added a mode to display spot savings vs on-demand.
Right. So the Show HN page says you can barely go below $5 per gigabyte with on-demand pricing. OVH RAM instances consistently cost 1.33 $/GB for a machine with 30, 60, 120 or 240GB of RAM.
I havent looked at OVH lately, but are they really a cloud? Do they provide full VPC with central firewall? Dynamic network disk storage that can be mapped to servers?
TIL, thanks! Didn't realize OVH was OpenStack--that's a pretty hard no for me, because I've witnessed firsthand the failure conditions there, but I appreciate the correction.
It's not NFS, it's a block storage mechanism. NFS presents a file-based interface, EBS is a block/device-based interface. The underlying implementation isn't widely publicized, but if you think about how a block device works on a Unix and the AWS bigger-is-faster model for non-PIOPS EBS, you can probably draw some reasonable inferences.
> For example, in at least some embodiments, a representative logical local block data storage device may be made available to an executing program via use of GNBD (“Global Network Block Device”) technology.
If all you need is compute and RAM, then OVH dedicated machines are a great choice; I used them for a long time myself and would again for personal stuff. That said, it's important to remember that focusing on that to the exclusion of turn-key services (RDS has saved clients of mine tens of thousands of dollars in billable hours just by itself) doesn't do you so well once you need more than that.
When they have RDS and Redshift and and Athena and SQS and SNS and when they have a fully-functional API that crosses every platform I need to write code against and years of a proven track record of stone-cold simplicity and success, I am sure I will take that into account.
Time is valuable. AWS/GCE/Azure have a huge head start in making us more productive.
> Another mistake was that when originally released Python 3 did not offer enough shiny new things to convince people that going through the pain of upgrading was worthwhile.
This is the core issue, but you're putting cart before horse a bit: if there's not much to gain from switching, why would any reasonable person switch? And, most importantly, why is it a problem that needs solving at all?
Crimes requiring some mental state other than specific intent are fairly common, not a special case (note that this includes murder of the depraved indifference sort.)
That one sounds fairly similar to manslaughter, no?
My understanding is that logically there's that basic framework of required specific intent, then there are a few crimes that allow prosecuting for negligence, then very few crimes with strict liability.
I'm originally not from US so I'm probably still getting used that the latter two categories are quite common in US law (and that strict liability is even possible).
Come on, if that was true they would never be able to hire tens of thousands of engineers. They do have high false negative rate (by design) but it is far from impossible to pass. I personally know a ton of people who were hired by Google after standard interview process.
Google has upwards of 50k employees. Compare that to IBM: upwards of 500k employees. A friend (and maker and seller of tech companies, so he's quite well connected, much better than I) living in Palo Alto has told me he knows of no one who works at Google in engineering who isn't an acqui-hire.
