Native Java engine
Status: Inactive
Brought to you by:
robgreayer
Fairly simply this is a proposal to replace the Haskell engine with a native Java one for maximum compatibility across platforms and removing the need for the extra build stage. I realise that Haskell is quite concise, but it seems there are few advantages to using it when a native Java component could offer greater performance and take advantage of more of the compilation/processing features of Eclipse to avoid overly long delays etc.