4.13. Future applications

4.13.1. The executable will die and the JavaScript will survive ¶

Compiled executables, such as C or Java compilations, cannot be run on different hardware.

Executable files (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 client computers.

我们的建议：

Use only HTML, CSS, and JavaScript to write your future applications.

Make sure your future application can run in any Web browser.

4.13.2. Web applications will become Internet Services ¶

In the past, applications were large applications created for specific purposes. Most of them will soon die out because they cannot provide services as the requirements change.

The application should be flexible, general-purpose, and well adapted to changes in requirements without being compromised.

Applications should be able to scale from supporting millions of requests every day.

Applications should be able to propagate and move between multiple servers without being compromised.

Applications should be able to be used with other applications.

The application should not contain a large amount of code. Applications should be broken down into smaller services to make them easy to create and maintain.

An application is a series of Internet services that can return data to submitted Internet requests.

Applications should request services through standard Internet protocols without maintaining a permanent connection to the server.

我们的建议：

Use the Internet based on SOA (Service Oriented Architecture Service oriented Architecture) to write your future applications.

Make your application services more generic, flexible, and able to serve different types of requests.

4.13.3. Future applications will be easy to create and edit ¶

The client and server will exchange data in an easy-to-understand way.

If it can be avoided, the application will not be encoded.

The application will create and modify by editing the model instead of editing the code.

The application description will be readable by humans.

The application description will be self-describing.

The application will be written by the user, not the programmer.

我们的建议：

Use human-readable text files to describe services and provide services by executing these descriptions.

Use text files, such as XML files, to describe the application.

Use text files, such as XML files, for data exchange.

Use HTML, CSS, and JavaScript to execute the application.

4.13.4. Three small Web developers. ¶

Once upon a time, there were three small Web developers developing a new Web site.

1. The first Web developer uses < AppML >.

2. The second Web developer uses his favorite server-side programming language.

3. The third is to use a professional enterprise Web development framework.

The first Web developer completed the demonstration in two days. After cooperation with users, the preliminary prototype was completed within a week. After two weeks of testing, a smart, fast and easy-to-use website is ready for release.

Six months later, the second Web developer prepared his website. But WWW has changed the requirements, so he is not satisfied with his website. The Web developer cannot make major changes to his project because it contains too much code. As a result, he began the development of version 2.

The third Web developer never did his job successfully. That professional Web development framework is difficult to use, difficult to understand, and almost impossible to test.

看一看第一个开发人员是如何做到的 .