2 ms·
It sounds like it's layered: =========JAVA========== ==C (SDL)== ==Haskell== Rather than: ===JAVA==== ==Haskell== ==C (SDL)== If that's
by dllthomas 12y ago
It sounds like it's layered:
=========JAVA==========
==C (SDL)== ==Haskell==
Rather than:
===JAVA====
==Haskell==
==C (SDL)==
If that's the case, I wouldn't expect much of a performance hit from the layering given that (as I understand things)
===Java==
==C/C++==
is common for people writing games.
You'll certainly have a memory hit of the Haskell runtime (though I'm not sure how that compares to the size of other relevant things), and the performance differential between Haskell and whatever you would have been writing that code in otherwise (presumably C or Java) - which could be in either direction depending on the details.
- chrisdone 12y agoHaskell runtime is about a meg in size. Rather, most memory use will come from additional libraries and garbage generated, I expect.