YouTip

# Future Applications * * * The following introduces the **Tutorial version of** future web applications. * * * ## Executables Will Perish, JavaScript Will Survive Compiled executables (like those from C or Java) cannot run on different hardware. Executables (EXE files, ActiveX and COM objects, DLL files) are components that prevent the development of applications running on the Internet. Future applications will not be able to use, or rely on, components installed on the client computer. **Our Recommendation:** Use only HTML, CSS, and JavaScript to write your future applications. Ensure your future applications can run in any web browser. * * * ## Web Applications Will Become Internet Services Past applications were large, purpose-built applications. Most of them will soon perish because they cannot adapt to changing requirements. Applications should be flexible, versatile, and adapt well to changing requirements without breaking. Applications should be scalable, from handling millions of requests per day. Applications should be able to propagate and move across multiple servers without breaking. Applications should be able to work together with other applications. Applications should not contain large amounts of code. Applications should be broken down into smaller services for easier creation and maintenance. Applications are a series of Internet services that return data in response to submitted Internet requests. Applications should request services via standard Internet protocols without maintaining a permanent connection to the server. **Our Recommendation:** Use SOA (Service Oriented Architecture) based Internet to write your future applications. Make your application services more generic, more flexible, and able to serve different types of requests. * * * ## Future Applications Will Be Easy to Create and Edit Client and server sides will exchange data in an easily understandable way. If possible, applications will not be coded. Applications will be created and modified by editing models instead of editing code. Application descriptions will be human-readable. Application descriptions will be self-descriptive. Applications will be written by users, not by programmers. **Our Recommendation:** Use human-readable text files to describe services, and provide services by executing these descriptions. Use text files (like XML files) to describe applications. Use text files (like XML files) for data exchange. Use HTML, CSS, and JavaScript to execute applications. * * * ## Three Little Web Developers... Once upon a time, there were three little web developers, developing a new website. 1. The first web developer used . 2. The second web developer used his favorite server-side programming language. 3. The third used a professional enterprise web development framework. The first web developer finished the demo in two days. After collaborating with users, he completed the initial prototype in a week. After two weeks of testing, a smart, fast, and easy-to-use website was ready for release. Six months later, the second web developer had his website ready. But the WWW had changed requirements, so he was not satisfied with his website. This web developer could not make major changes to his project because it contained too much code. So, he started development on version 2. The third web developer never successfully finished his work. That professional web development framework was difficult to use, hard to understand, and almost impossible to test. (#).