Yes! I had the exact same reaction to this story. The way I interpreted the story is that the design of the Versa may actually have contributed to his wife's safety. It's possible the car was designed to crumple in such a way to distribute the weight of the collision. Ironically getting a Crown Victoria may decrease the overall safety.
According to https://www.ncbi.nlm.nih.gov/pubmed/24073770 (fire-related auto deaths in Sweden), this is a problem. Around 5% of auto-related deaths in Sweden involved burning cars, and around 1/3 of these deaths fire was the cause of death. Definitely not the main cause of death, it is a factor that has to be considered when looking at overall safety.
I would argue that a Nissan Leaf would be overall safer than a Crown Victoria.
First of all, the 2nd generation (2018/2019) Nissan Leaf seems to have a comparable weight as the Crown Victoria. From the data I've been looking at online, it's around 25% less weight than the CV, but definitely more than a Versa. Also, this weight is likely better distributed throughout the car instead of being concentrated in one place.
Another factor to consider is that the CV is an older vehicle (did they stop making them in 2012?), and in general newer cars are safer due to strong materials and safety features/design.
Also, the likelihood of a fire during an accident is greatly reduced (although still non-zero, as demonstrated by Tesla).
"There are three gates leading to this hell — lust, anger and greed. Every sane man should give these up, for they lead to the degradation of the soul." - Bhagavad Gita
Wow, I didn't expect this to make the top of Hacker News :)
Web.go is a wrapper on top of Go's net/http standard library. The authors of Go aren't from a web programming background, and the net/http server interfaces was a bit more clunky than I'd like, which is the main reason web.go exists. It's not really designed to be a full-fledged web framework.
I used it to build a few apps. There's an old article about one of them here (although the app has since been taken down):
Yes, it was definitely inspired by web.py (tornado, actually). I loved tornado but didn't like the fact that there were no asynchronous libraries for it.
It is a little worrying that if some (perhaps inexperienced) developer arbitrarily calls a method that invokes Ruby's select, the process will crash mysteriously.
Doesn't Ruby have a limit of 1024 open file descriptors? If some method in Ruby's standard library calls 'select' internally, with the 1024 limit, what happens?
Programming all day isn't what our bodies are genetically designed to do. Programming involves countless hours of ruminative thoughts, and limiting human contact, and stress, all of which are ingredients for mental illness.
For simple projects or toy apps, gofix is just fine. However, some companies are running complex production systems written in GO 0, and the code may have a lot of dependencies and custom build scripts. In this case it's useful to have an easy way to install and pin Go versions.
Once Go 1 launches, subsequent releases should be compatible with the Go 1, which reduces the need for something like GVM.
There probably is a market, but it's a lot smaller than building general web/mobile applications.
The kind of clients that want to build an API 1) already have a main product/website and 2) are likely more technical than average. It's probably something they could do themselves.
I've known Matt for a while; he's a regular at the weekly Ruby hack nights in SF and we've worked together on some small projects. He has a great product sense and an extensive background in user acquisition strategies. This is a great opportunity for someone looking to join a startup.