> Although the language has significant benefits to the programmer, the execution speed and size of
> Java-developed applications limits its use in measurement and automation.
Hmm, and they (NI) provide solutions for... Visual Basic! (whose drawbacks, part from poor thread handling and unreadable syntax, are listed above, only it is there referred to as "Java").
Any JVM will beat VB in execution speed and size for any app. Either a java app's is judged from the size of the code or of the the runtime, in which case (the latter), the vb app should be estimated to be half the size of the winnt folder.
Well, on to my question, is anybody out there controlling the NIDAQ1200/... from java? I'm in a situation w
here our app has, spite being small, long ougrown the possibilities of VB (i.e. it uses >1 actual threads and the UI is suffering BAD, buttons not responding, etc.) and I contemplate porting it to java to simplify threading, file io, graphics, calculations, etc...
Well, has anybody done it? Has anyone created interfaces already (as seen above, NI seems to have missed the Java movement)? Are there packages of wrappers (C++ to java) available (for Sun or MS)?