345 karma · joined May 1, 2014
Also, complementing toomuchtodo's comment, there's also now EBS types focused on almost all kinds of workloads: sc1 for cold data/archiving, st1 for workloads optimized for sequential scans (a Confluent benchmark even reported that Kafka ran better with st1 EBS than instance storage), io1/PIOPS for databases and gp2 for everything else.
I don't think English is much better in these cases. In fact, the writing can be so divorced from speech that spelling bees are a thing.
(I'll probably take a stab at writing one this weekend, though)
The Hadoop FileSystem interface doesn't really force an specific underlying implementation, and you can even use "local" filesystems without any issue, in fact, IIRC, MapR-FS is just an optimized NFS drive, i.e. a shared network drive.
Specter[1] provides something like this for Clojure, allowing rich navigation and transformation abilities to deeply nested structures.
[1]: http://nathanmarz.com/blog/functional-navigational-programmi...
Not that much in Go 1.5 :) On the last project I worked, just setting GOARCH and GOOS worked out of the box.
- I've seen my fair share of columns typed as fixed-width NCHAR. Yeah, a "89.99" order total you see on the screen might be stored internally as `000000000089.99`.
- Booleans? Why not use `x`, ` ` and `#` instead of true, false and null?
var h: Option[String] = Option("Hello")
or import scalaz (in case you have it in your classpath etc): import scalaz._, Scalaz._
var h: Option[String] = "Hello".some