At 2002-03-11 15:16, Mark Carroll wrote:
One criticism I've received of the suggestion that we use Haskell in our business is that some particularly large clients will demand code in some 'standard' language that they know they can deal with, especially if they end up stuck with the software and we stop supporting it.
That's very reasonable, actually.
How are others dealing with this? How big a project would it be to translate, say, from Haskell to C or Java?
Huge. IMO, you'd probably need to rewrite everything. On the plus side, Haskell is typically excellent for exploring any problem domain. So you might end up with better designed and more maintainable Java or C code than you would if you started from scratch. Or not. -- Ashley Yakeley, Seattle WA