I’d love to hear some comments from other experienced Haskellers about the article, and see more articles like this as well: it’s a long way from a quicksort 3-liner to a real-world application for newcomers like me, and posts like this one really help.
Good overview of the design issues in what is doubtless an enormous program. One thing that Haskell does really well, which wasn’t addressed, is break up large programs into multiple small libraries. I use Haskell in my day job, and often grapple with the question of where exactly to draw the line between program-chunks. In a corporate setting, the pressures on that are different than they are in open-source work, and it would be fun to hear somebody else’s take on this.
I would also have enjoyed discussion of what sorts of interfaces the major components were connected through - Haskell function calls? Web services? Raw sockets? Stdio pipes? If Haskell calls, with what sorts of signatures - who provides the monad that things are done in (caller or callee), how much emphasis does the codebase place on being parametric over monads, that sort of thing.
(Also, heh, gender-exclusion issue in the name of the simulator. People can imagine what I think; I don’t want to get involved. Which might tell observant folk something!)
I’d love to hear some comments from other experienced Haskellers about the article, and see more articles like this as well: it’s a long way from a quicksort 3-liner to a real-world application for newcomers like me, and posts like this one really help.
Good overview of the design issues in what is doubtless an enormous program. One thing that Haskell does really well, which wasn’t addressed, is break up large programs into multiple small libraries. I use Haskell in my day job, and often grapple with the question of where exactly to draw the line between program-chunks. In a corporate setting, the pressures on that are different than they are in open-source work, and it would be fun to hear somebody else’s take on this.
I would also have enjoyed discussion of what sorts of interfaces the major components were connected through - Haskell function calls? Web services? Raw sockets? Stdio pipes? If Haskell calls, with what sorts of signatures - who provides the monad that things are done in (caller or callee), how much emphasis does the codebase place on being parametric over monads, that sort of thing.
(Also, heh, gender-exclusion issue in the name of the simulator. People can imagine what I think; I don’t want to get involved. Which might tell observant folk something!)