I find it very interesting that so many folks are looking at the poor "side effects" of Java as a Web site interface and standard. Yes I agree it can often be slow to load and in this day and age of instant click response expectations annoying when I am visiting a Java Applet6 integrated website. However, as an account/client manager for a larger IT solution firm who handles accounts with expenditures from small to large ($25,000/year hardware spend to over $10 million - I point this out as a reference to varied infrastructures we encounter), Java is no where from disappearing as a very strong intranet portal background. Without naming corporations, I currently have several multi billion dollar accounts that have recently moved to using an IBM or BEA SOA solution to port many applications for internal employees to a Java platform. More so than any other solution base for creating an enterprise wide standard without hab=ving to resort to expensive MS Enterprise agreements. These SaaS portals for employees provide simple collaboration and eliminate the need to be concerned with version compatibility.
I have seen many of these continue to focus on this as a way to avoid the complexity of compliance issues (an older PC user with say Office 97, is not allowed to access a server that uses a later version of MS Office to process data, really!) By creating Java SaaS for employees and having the servers perform the heavier crunxching, Java provides many enterprise IT dept's with a strong reliable and Highly available alternative to deploying various different applications and compatibility issues.
Just one man's observations. I still think a company must choose what they are most comfortable. And yes I hate the wait for applets to load, ok!
Slashdot Mirror
I find it very interesting that so many folks are looking at the poor "side effects" of Java as a Web site interface and standard. Yes I agree it can often be slow to load and in this day and age of instant click response expectations annoying when I am visiting a Java Applet6 integrated website. However, as an account/client manager for a larger IT solution firm who handles accounts with expenditures from small to large ($25,000/year hardware spend to over $10 million - I point this out as a reference to varied infrastructures we encounter), Java is no where from disappearing as a very strong intranet portal background. Without naming corporations, I currently have several multi billion dollar accounts that have recently moved to using an IBM or BEA SOA solution to port many applications for internal employees to a Java platform. More so than any other solution base for creating an enterprise wide standard without hab=ving to resort to expensive MS Enterprise agreements. These SaaS portals for employees provide simple collaboration and eliminate the need to be concerned with version compatibility. I have seen many of these continue to focus on this as a way to avoid the complexity of compliance issues (an older PC user with say Office 97, is not allowed to access a server that uses a later version of MS Office to process data, really!) By creating Java SaaS for employees and having the servers perform the heavier crunxching, Java provides many enterprise IT dept's with a strong reliable and Highly available alternative to deploying various different applications and compatibility issues. Just one man's observations. I still think a company must choose what they are most comfortable. And yes I hate the wait for applets to load, ok!