Conversation

Notices

1. Embed this notice
   洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Friday, 25-Aug-2023 01:16:49 JST 洪 民憙 (Hong Minhee)

   This is why I've considered #PureScript as a decent alternative to #Haskell, but it's overly centered on the web and Node.js (it has a Go/C++ backend, but it's never a first-class citizen), and the lack of momentum due to the size of the community makes me scared to bet on it. 😇

   https://journal.infinitenegativeutility.com/leaving-haskell-behind

   • Embed this notice
     Boyd Stephen Smith Jr. (boydstephensmithjr@hachyderm.io)'s status on Friday, 25-Aug-2023 05:12:20 JST Boyd Stephen Smith Jr.

     in reply to

     @hongminhee IME, the tooling with #PureScript is actually worse than the tooling with #GHC #Haskell, which really seemed to be the main problem raised in the article.

     I haven't played around with the latest and greatest web backends for GHC, but I did try GHCjs and PureScript at the same time, and felt PureScript was already ahead of the game then. But what other people tend to call "tooling" (I find the concept nebulous) has never seemed to be a priority for me.

     洪 民憙 (Hong Minhee) repeated this.
   • Embed this notice
     Anupam 《ミ》λ≡ (haskman@functional.cafe)'s status on Friday, 25-Aug-2023 12:04:34 JST Anupam 《ミ》λ≡

     in reply to

     • Boyd Stephen Smith Jr.

     @BoydStephenSmithJr @hongminhee Tooling with #PureScript is *way* better than #Haskell's. IDEs work flawlessly, and spago is more like cargo than cabal. I find PureScript development much more soothing than when I have to write Haskell.

     The only caveat is that the tooling is currently being upgraded (new registry, spago-next) so there may be some teething troubles if you use the new infra.