I'd object to your implication that Haskell is completely ready for use in general soft real-time systems. I was unable to implement a multi-threaded application which does a some IO-work in background threads in a way so that its GUI won't die. Worker threads simply starve the GUI, because Haskell doesn't have thread priorities. And even if it had, it would still lag on Windows, due to lack of IO manager. Ezyang had, in fact, made a new scheduler, which seems to address the problem; and joeyadams tries to make IO-manager for windows, but all this isn't going to see the light of day for a while, at least until 7.8.1.
2013/1/31 Ertugrul Söylemez <e...@ertes.de>: > That used to be true, but the reason has nothing to do with the > language. The problem was that the libraries weren't there. Nowadays > you can write all sorts of interactive applications in Haskell, > including GUIs, TUIs, games, simulations and web applications. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
