PHP Daniel talk about the future of PHP infinite reverie

The German Open source software developer Frank Karlit-schek-led Owncloud project is one of the largest open source projects currently written in PHP. He mentioned the following points when he talked about why PHP was chosen.

Universality: The purpose of owncloud is to allow everyone to host their own cloud servers. PHP is now widely used in Web servers, operating systems, the advantages of the platform so that users can easily deploy.

Versatility: As a scripting language, a server tar file can run on all platforms without complicated additional compilation.

Low threshold: Most programmers are not familiar with PHP, even 0 basic users, learning PHP is relatively easy.

Lightweight and powerful: PHP runs fast and powerful as long as it's used properly. Wikipedia, Facebook, WordPress and other large Web applications are written in PHP.

Resource-rich: PHP has a huge ecosystem of development, including libraries, components, connectors/drivers, and more. Using it is like standing on the shoulders of giants.

But even though PHP has these bright advantages, Frank also points out that it has shortcomings.

Security: As the product of the the 1990s, its security performance is not reassuring, after all, people's safety awareness is relatively naïve.

Compile time/runtime configuration: called./configure script to build PHP at your own whim sounds interesting, but if you're thinking about transposition, we need to look at other people's scripting configuration word for word while maintaining it.

Contradictory functions and class naming: The moment is underlined, the moment is the hump named; some features can be process style or object-oriented interface style, or even both.

Static type: PHP can do better on static types.

Recently, Apple's new development language, Swift, touches Frank, is the language needed to be backwards-compatible or completely innovative when it comes to renewal? And if it is similar to Perl and Python can not be compatible, the final parting of the situation, we do not want to see. In this respect, Frank puts forward his own ideas on the future of PHP.

Security: Discard _get, _post, _server, and introduce a suitable API to filter data input.

Database: PHP's database Support API is really rich. But some APIs are very old and outdated. Frank recommends standardizing this and eventually creating a unique object-oriented interface. PDO was the first attempt he made.

32-bit/64-bit: When running PHP in 32-bit or 64-bit, people will find out the difference in the operation of the integer data in particular. It is necessary to eliminate the operational differences between different types of systems.

Eliminate traditional concepts such as Save_mode, Open_basedir, and use Unicode characters.

Remove most of the options for compile and run-time configuration: All of the next generation of PHP's runtime environment should be as uniform and stable as possible.

Type: the introduction of optional static types must be very exciting. In this case, a variable can be defined as Boolean or reshape. If a variable is used incorrectly, an exception is thrown.

HPE offers PHP professional development ide--phpstorm (currently at the end of the year to enjoy the benefits). Also have the discount wish, oneself want how to discount on how to discount. "The peak of the year-end promotion" Hui "?" Iphone?6? Plus, Iphone?6, IPad? Air is full to send, not quickly buy buy buy!

PHP Daniel talk about the future of PHP infinite reverie