ScalazコミッターからみたScala Slick

Brian McKenna @puffnfresh

#Scala Slick is the perfect example of a library which is actively against all attempts at abstraction. Try to avoid it.

Brian McKenna @puffnfresh

@curious_reader path dependent types, queries can be mapped, tables and columns can't, implicit conversions which remove safety, much more.

Brian McKenna @puffnfresh

@clementd we use Slick, but it's very poor. All alternatives also seem very poor but probably not to the same extent.

Brian McKenna @puffnfresh

@cwmyers don't have one. Vault and Doobie might be more sensible but fundamentally JDBC is broken, so building on that can't be great.

@pchiusano@universeodon.com @pchiusano

@puffnfresh @runarorama The mistake with Slick: thinking that making your first-order syntax pretty is the goal of a library

Rúnar @runarorama

@pchiusano @puffnfresh This is unfortunately common with Scala libraries. Goddamn “fluid interfaces“ and English-looking DSLs.

Brian McKenna @puffnfresh

@rtfeldman @jfklingler @runarorama @pchiusano obviously English is the language to aspire to. Ambiguity is great!

Brian McKenna @puffnfresh

@tbraje @pchiusano @runarorama it'd be more sensible for us to use either: github.com/markhibberd/va… or github.com/tpolecat/doobie