Clojurians Log v2

What did Rich Hickey mean with “types are parochial”? What does parochial mean in that context? I’m not a native speaker, but even looking it up in a dictionary doesn’t fully explain it to me.

What I think he means: types force you to choose a name for a combination of attributes and attributes from different types don’t merge

so the type “governs” the set of attributes?

Pragmatic “app” monad in Haskell :thinking_face:

newtype AppM a = AppM (LoggingT (ReaderT Context (ExceptT AppError IO)) a)
    deriving ( Functor, Applicative, Monad, MonadIO
             , MonadError AppError, MonadReader Context, MonadLogger)

@borkdude that's my interpretation as well.

or as Brandon put it recently: https://twitter.com/BrandonBloom/status/935570873699909633

I read the tweet also recently, but didn’t fully grok it

but I recognize the feeling of “this would never be a problem in Clojure” when working with typed languages 😉

@borkdude Not sure if it helps but Rich means "parochial" in terms of "narrow scope or outlook" and I took it to mean that types are usually very focused and restrictive, so code is less reusable across domains -- compared to dynamically typed code that can operate on many different concrete types.

Specifically, when you define a class type to represent a data structure, you end up with a set of operations on that class type -- that cannot be used on similar data structures that have a different type. Whereas we have operations on "collections" and "sequences" because we use data instead of specific types of data.

I'd never thought of types that way until I heard Rich say it -- it was sort of a light bulb moment for me (which his talks often are).