Sudhir Kumar

@saurabhnanda This immediately brings up horror stories... 1. Security issues 2. Performance 3. Complexity I believe if you need flexibility in selecting the fields then we can use GraphQL (http://graphql.org/)...

I mentioned GraphQL as it might be useful for your use cases. - GraphQL has a server side which in turns fetches data from API endpoints - Haskell server not...

@saurabhnanda if you really want to implement this, then I can think of a way. 1. Limit the fields that can be mentioned in the "fields" QueryParams using ADT? 2....

@saurabhnanda Before I make comments on the SPEC document. I just want to collect my thoughts and also share them with you. So that you know my perspective. I believe...

@saurabhnanda We have already started working with PureScript and we are using PureScript Pux (https://github.com/alexmingoia/purescript-pux). PureScript is very close to Haskell. Its not Lazy though! https://github.com/purescript/purescript/wiki/Differences-from-Haskell We are using React...

> Would you rather deal with orchestrating micro-services in production and dealing with a distributed system OR would you put extra effort in closing the library gap in Haskell? As...

@saurabhnanda I am having second thoughts about using Tests vs Type System to enforce correctness. I am more concerned about being able to jump right into the projects along with...

@saurabhnanda I found helics for New Relic (https://hackage.haskell.org/package/helics) Airbrake :: https://hackage.haskell.org/package/airbrake

Just my 2 cents! @saurabhnanda we can have these data declared in different NameSpaces and if we do then we might have to alias the module when we import T.Active...

@saurabhnanda I believe Option 1 is the best choice as the product details for the customer will be different from that of the Admin. I would go with Option 1....