Why to use TioLink
Why to use TioLink, why to use a Java VM if you can have the D performance?
- Java has so much libraries and frameworks. TioLink makes them accessible for you, without porting. Porting Java code is possible (see TioPort) but has disadvantages and limits.
So if a big library like SWT is ported from Java to D, the D executable size grows a lot, and the resulting code is not more efficient as the Java original. This is, because the ported code also needs to emulation all Java behaviour.
Porting has its limits, in cases where the java code heavily depends on Java internas. E.g. OSGi makes use of own classloaders. Automatic porting in this case is not possible, because D cannot emulate this behaviour.
- Performance must not be killed by running a VM.
If the performance critical loops and operations are implemented in D, but the GUI is handled by a performant Java implementation, the can be a win for all: Java, D and the user.