3 ms·

it is hard to read if you don't have some knowledge of haskell indeed and the comments part is true but it's not any harder then folowing other codebases if you

it is hard to read if you don't have some knowledge of haskell indeed and the comments part is true but it's not any harder then folowing other codebases if you don't know the particular language so i don't think this is a strong argument. Another point is - it's not a library and you are not the one maintaining it :) the same way you are not maintaining, but still using things like postgresql,nginx,redis, rabbitmq. I bet it's a lot easier to learn haskell and patch postgrest then to know C for 10 years and patch postgresql :)

antpls 7y ago
> you are not maintaining, but still using things like postgresql,nginx,redis, rabbitmq I don't maintain them because they are written in either C or C++, which has many more practitioners, guidelines and tools to trust. On the other hand, I can easily see people using postgres' extensions have to quickly make a patch to fix a bug or change a behavior, extensions being smaller. The issue is that, eventually, you would like to patch, review or audit the extension. All of these operations will require you to find third-party Haskell developers, Haskell auditors, Haskell reviewers, who are rare in the job market, and therefore it represents a risk for your project. If the core developers stop to maintain the extension, no one else might be available to maintain it, and now you have code debt and code that no one can fix
- ruslan_talpa 7y ago
  > no one can fix Really? No one? I learned haskell (my first FP lang) and rewrote the core of PostgREST (in my spare time) in about 6m... so stop scaring people :)