rokekr
At these Go meetups, companies are presenting what they're using Go for in production already, with great success. Go is not difficult to program in, Go is functional, Go is performant, Go is developer friendly.
That is not to say that Go doesn't have warts, it does (32-bit garbage collecting anyone? or the slow regular expression engine?), but people from Ruby, people from Python, and people from JavaScript are gravitating toward Go and _enjoying_ it.
Go also has excellent stewardship in the form of Pike et al.
In my mind, at least, the gap between Rust and Go is pretty big at this point. This is why Rust feels like vaporware (especially compared to Go).
People like to compare Go and Rust, and I think the comparison is pretty natural. The difference is that Go already has "boots on the ground."
If Rust releases something awesome in the next few months, the gap between Go and Rust could rapidly close (depending on developer adoption). But, in my mind, the longer Rust takes to iron out the quirks of it's syntax (not implementation, syntax!), the wider that gap will get.
If the landlord found out why her place was vandalized, he may have grounds to boot her out of the apartment.
Not to mention the theft of personal documents and potential theft of identity. The (very real) potential of being bushwhacked by additional fraud years down the line due to this incident is pretty horrifying.
We're working on getting this fixed as soon as we can.