4 ms·

What's the point of the article then. Is there any language that can't fire off a billion syscalls that enter a wait assuming it's purely IO bound?

• wyager 10y ago
  Have fun programming that in most languages, especially if you're doing some non-trivial combination of IO activities. Haskell's runtime allows you to program in a convenient and clear threaded style and automagically takes care of efficient polling and dispatch and such. If you want to write a web application in around some giant epoll loop, more power to you. Have fun with fairness guarantees, buffering, ensuring that connections don't time out because you're favoring certain connections...
  • banachtarski 10y ago
    I'm actually pretty fluent in Haskell but you're overselling it in my opinion. Haskell also has issues with fairness guarantees and as for buffering and timeouts and stuff, I have less control than I would in a language like C. Also, epoll really isn't that hard.
    • willtim 10y ago
      C is the right choice for some performance critical domains, but productivity will be a long way from what a Haskell developer can achieve, especially when concurrency is thrown into the mix. IMHO, I think you are overselling C.
    • deleted 10y ago
      [deleted]