Re:PostgREST – A fully RESTful API from any existing Postgre...
by cgag on Sunday March 26, 2017 @07:36AM
(#13960261)
It's not like putting the code on one line. It's like complaining about using map instead of a for loop but you don't know the abstractions.
There's a line of too much abstraction, and lots of.haskell code crossed it, but the postgres code ive looked at doesn't seem to suffer from it.
Also I really hate the types are documentation people, but I mean it's hard to argue with it for asking about what transformation is happening.
Edit: also if be surprised if those numbers are all that bad if you consider the size of the codebase but yeah it's hard to get contributors to a Haskell code base.
There's a line of too much abstraction, and lots of.haskell code crossed it, but the postgres code ive looked at doesn't seem to suffer from it.
Also I really hate the types are documentation people, but I mean it's hard to argue with it for asking about what transformation is happening.
Edit: also if be surprised if those numbers are all that bad if you consider the size of the codebase but yeah it's hard to get contributors to a Haskell code base.