3 ms·
PureScript made some ergonomically painful decisions (I value the logic behind their implementation of tuples but not having to use them in such a way), but I t
by wryoak 3y ago
PureScript made some ergonomically painful decisions (I value the logic behind their implementation of tuples but not having to use them in such a way), but I think the biggest point against it is how Haskell is moving into that space via JS and WASM compiler targets and bringing along its broader user base and library support
- ddellacosta 3y agoYeah the way tuples work in PS is kinda painful, but there are some affordances for tuple-like pattern matching that smooth over some of that pain. On the other hand, I feel like PureScript's records that utilize row polymorphism are such a game changer that it's hard for me not to get frustrated with Haskell records when I go back. And while I love where Haskell is going with WASM and JS support, I think it'll be a little while before that is viable for real-world projects.
- whosthatguy 3y ago> Haskell is moving into that space via JS and WASM compiler targets and bringing along its broader user base and library support This has been an initiative for longer than PureScript has existed. I wouldn't expect it to replace PureScript any time soon to be honest.