Linked by Andy Roberts on Thu 19th May 2005 19:33 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



At my workplace, the company is in the process of deploying a new client/server java app which wil replace an old visual basic app we have depended on for years. There is some grumbling about performance (it took years for the visual basic app to overcome it's performance issues), but no complaints about look and feel really. A button is a button, it's just the unfamiliarity of the new interface layout that is a concern right now.
I rather appreciate the fact that we are moving to a java client though, for the reason that we will theoritically be free to deploy on other operating systems if desired at some point in the future. We could mix client machines, even have a few Macs in there and the application should still work, even though it may look a little funky.
On my home machine though, I don't enjoy running java applications. Even though I have come across a few programs like Oxygen that would be useful to me, I can't see myself spending money to purchase a copy. I imagine how much better the software would be if someone could just write a native version for my computer. I would even give up some of the feature set just to lose some of the interface 'wonkiness' of the java version. By having the single cross-platform code-base, the developers have been able to concentrate on maximizing features, but that's not good enough for my money. I would rather have the application that targets my machines native features.
Now that the hype of Java has died down, it's easy to see that Java wasn't intended as a cure all for the world of application design. It was a toolset that solved a need for Sun. It is the application layer that let Sun create enterprise applications that could be deployed on both Solaris and Windows. They allowed others (like Apple) to license the kit so they had the opportunity to participate in that world, but Sun's interest only extended as far as those two platforms they needed for their own interest. And for that purpose Java is OK.