>It can be gui but ive written lots of Java that is not gui at all. Java is
>just a replacement code for C that is more portable.
And MUCH slower. I think that Lucent is missing the boat here. Most of
the current command line utilities are not used solely from the command
line, but also from much larger scripts that may be polling 20 or 30 PM's
every other minute or so and then pretty printing the output. In that
case, going to Java is a big disadvantage. I don't mind them getting
tired of supporting several platforms and wanting to make it easy on
themselves by going to Java. Java is never done for the benefit of the
end user but for the convenience of the programmer/administrator. Why not
document the interface and let us code our own C to talk to it?
As for Java being less buggy, I haven't seen that in current Java code at
all. Most Java apps I've seen are riddled with bugs. (Just not ones
dealing with pointers from user code, although I've seen tons of pointer
errors from poorly written interpreters themselves). Amber is nice, but
if it is one thing, that one thing is SLOOOWWW.
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>