@-=[(ELVIS)]=- sure, current development is not future-proof. Here are my thoughts about it:
- I can't rewrite TDUF in another language, given amount of code in it.
- TDUF already relies on some TDUMT executable to handle BNK files
-.net and c++ apart, there is no way of running app in windows without it requiring an embedded runtime (Java, python, Ruby, js, etc...).
So for the future I'm considering 2 development aspects:
- maintenance and evolutions of TDUF will embed their own JRE, or will use a JRE which will be provided as separate download and will have to be extracted into tduf directory
- new tools based on TDUF might be written in different languages but like above, a runtime will be available or integrated (e.g JavaScript can run in an electron desktop application - at the cost of file size).
Other ideas? Thanks for feedback.