Scripting's Future: Who says it's important? Some scripting plans of many of the well-known companies in the industry: IBM Granddaddies of scripting with Rexx, with declared support for providing open scripting in the languages that people prefer to use, probably covering at least the Rexx, C/Java, and BASIC syntax families over time. Microsoft ASP uses Active Scripting to support any script language in server. Internet Explorer supports JavaScript. Pushing VBA to add VB to third-party applications. New Windows 98 desktop is made primarily of scripted components, allowing them to try new paradigms faster and to allow customers to turn the desktop into a customized application. With Windows 98 scripting is now part of the OS. Netscape All Netscape components, client and server, are controlled with JavaScript, even the system initialization files. Visual JavaScript combines the various Netscape services as components (represented as JavaScript Beans) into a single application. Client and server development from a single visual interface. Novell With UCS, all Novell APIs and services are controlled as objects through scripting (language-independent). The scripting interface lets services extend between servers and between the servers and clients. NDS used for script distribution and security from and between any system anywhere. Sun Continue work on Tcl/Tk, with speed improvements due to compilation. Linking Java to script languages. Has announced future integration of JavaScript with the JVM. By looking at where the major players are headed, we can see where the momentum is: the momentum is clearly with scripting. In addition to the points mentioned above, all of these companies are working with standards bodies such as W3C, OMG, and ECMA to define the direction of scripting for the future. Most of the companies listed above have contributed to this presentation.