The ownCloud project led by frankkarw.schek, an open-source software developer in Germany, is one of the largest open-source projects written in PHP. He mentioned the following when talking about why PHP is selected. Universality: ownCloud aims to allow everyone to host their own ECs instances. PHP is widely used in Web servers, operating systems, and platforms.
The ownCloud project led by Frank karw.schek, an open-source software developer in Germany, is one of the largest open-source projects written in PHP. He mentioned the following when talking about why PHP is selected. Universality: ownCloud aims to allow everyone to host their own ECs instances. PHP is widely used in Web servers, operating systems, and platforms.
The ownCloud project led by Frank karw.schek, an open-source software developer in Germany, is one of the largest open-source projects written in PHP. He mentioned the following when talking about why PHP is selected.
- Universality: ownCloud aims to allow everyone to host their own ECs instances. PHP is widely used in Web servers and operating systems. The advantages of the platform allow users to easily deploy PHP.
- Versatility: As a scripting language, a server tar file can run on all platforms without complex additional compilation.
- Low Threshold: most programmers are familiar with PHP. It is relatively easy to learn PHP even for users with no basic knowledge.
- Lightweight and powerful: PHP runs fast and powerful as long as it is used properly. Wikipedia, Facebook, WordPress, and other large Web applications are all written in PHP.
- Rich resources: PHP has a huge development ecosystem, including class libraries, components, connectors/drivers, etc. Using it is like standing on the shoulders of giants.
However, even if PHP has these bright advantages, Frank also points out its shortcomings.
- Security: as a product of the 1990s S, security performance is not reassuring. After all, people's security awareness was naive at that time.
- Compile time/runtime configuration: called. /configure scripts compile PHP as you wish. It sounds interesting, but if you think differently, we need to view other people's script configurations word by word during maintenance, which is not so beautiful.
- Conflicting functions and class naming: The name is an underscore at the moment, and the name is a camper; some features can be a process style, object-oriented interface style, or even both.
- Static type: PHP can do better in static type.
Recently, Apple's new development language Swift has touched Frank. Does the language need to be backward compatible or completely innovative when it is updated? However, if Perl and Python are not compatible with each other, you may not want to see them. Frank put forward his own ideas on the future of PHP.
- Security: discardGET,POST and _ SERVER introduce an appropriate API to filter data input.
- Database: PHP database support APIs are too rich. However, some APIs are outdated or even outdated. Frank recommends that you standardize the interface to form a unique object-oriented interface. PDO is his first attempt.
- 32-bit/64-bit: when PHP is run on 32-bit or 64-bit, the running difference, especially for integer data, will be found. It is necessary to eliminate the differences between different types of systems.
- Remove saveMode, openTraditional concepts such as basedir use unicode characters.
- Remove most of the compilation and runtime configuration options: the runtime environment of all next-generation PHP should be as unified and stable as possible.
- Type: the introduction of optional static types must be very exciting. In this case, a variable can be defined as a Boolean OR integer. If a variable is incorrectly used, an exception is thrown.
The author Frank Karlitschek is the ownCloud initiator and a free software developer.
Original article: http://karlitschek.de/2014/10/a-possible-future-for-php/
This article is compiled for programmer
Original article address: some possibilities for PHP in the future. Thank you for sharing it with me.
