Skip to content

Develop your website

Are you an enterpreneur and want a website to promote your buisness?

If yes please choose your catogery so that you can feel easy.

I need a attractive website i can invest required ammount
I need a simple website and invest less

Attractive website

I can develop a website that explores everything of your buisness or profession you just need to bive me the detailed information of your buisness and i will evaluate it and decleare price if you agree to pay the work is started and will be completed within a month to 6 month as per expansivity of site 

Simple Website

I can also develop a simple website which will be informative source of your buisness and some speical features will be mentioned in site

Note i will also give you a cms

comment if you are intrested

Trending Social media

E-sathi is a trending social media alternative to facebook is now available thus have a one.

About

Why e-Sathi exits?

Great artists

Terms of esathi

Basic Terms:

  1. Using this social networking platform implies your acceptance of these conditions. If you do not fully accept them, your entry to this site will be considered unauthorized and you will have to stop using it immediately
  2. You must be 13 years or older to use this site.
  3. You are responsible for any activity that occurs under your screen name.
  4. You are responsible for keeping your account secure.
  5. You must not abuse, harass, threaten or intimidate other e-Sathi users.
  6. You are solely responsible for your conduct and any data, text, information, screen names, graphics, photos, profiles, audio and video clips, links ("Content") that you submit, post, and display on the e-Sathi service.
  7. You must not modify, adapt or hack e-Sathi or modify another website so as to falsely imply that it is associated with e-Sathi
  8. You must not create or submit unwanted email to any e-Sathi members ("Spam").
  9. You must not transmit any worms or viruses or any code of a destructive nature.
  10. You must not, in the use of e-Sathi, violate any laws in your jurisdiction (including but not limited to copyright laws).

General Conditions:

  1. We reserve the right to modify or terminate the e-Sathi service for any reason, without notice at any time.
  2. We reserve the right to alter these Terms of Use at any time. If the alterations constitute a material change to the Terms of Use, we will notify you via internet mail according to the preference expressed on your account. What constitutes a "material change" will be determined at our sole discretion, in good faith and using common sense and reasonable judgement.
  3. We reserve the right to refuse service to anyone for any reason at any time.
  4. We may, but have no obligation to, remove Content and accounts containing Content that we determine in our sole discretion are unlawful, offensive, threatening, libelous, defamatory, obscene or otherwise objectionable or violates any party's intellectual property or these Terms of Use.
  5. e-Sathi service makes it possible to post images and text hosted on e-Sathi to outside websites. This use is accepted (and even encouraged!). However, pages on other websites which display data hosted on e-Sathi must provide a link back to e-Sathi.

Copyright (What's Yours is Yours):

  1. We claim no intellectual property rights over the material you provide to the e-Sathi service. Your profile and materials uploaded remain yours. You can remove your profile at any time by deleting your account. This will also remove any text and images you have stored in the system.
  2. We encourage users to contribute their creations to the public domain or consider progressive licensing terms.

FACEBOOK's TERMS and CONDITIONS

When ever you sign up in social media you must know it's terms and conditions
Here terms and conditions of one of the most popular social media FACEBOOK  is given

This agreement was written in English (US). To the extent any translated version of this agreement conflicts with the English version, the English version controls.  Please note that Section 16 contains certain changes to the general terms for users outside the United States.
Date of Last Revision: January 30, 2015
Statement of Rights and Responsibilities
This Statement of Rights and Responsibilities ("Statement," "Terms," or "SRR") derives from the Facebook Principles, and is our terms of service that governs our relationship with users and others who interact with Facebook, as well as Facebook brands, products and services, which we call the “Facebook Services” or “Services”. By using or accessing the Facebook Services, you agree to this Statement, as updated from time to time in accordance with Section 13 below. Additionally, you will find resources at the end of this document that help you understand how Facebook works.
Because Facebook provides a wide range of Services, we may ask you to review and accept supplemental terms that apply to your interaction with a specific app, product, or service. To the extent those supplemental terms conflict with this SRR, the supplemental terms associated with the app, product, or service govern with respect to your use of such app, product or service to the extent of the conflict.
  1. Privacy

    Your privacy is very important to us. We designed our Data Policy to make important disclosures about how you can use Facebook to share with others and how we collect and can use your content and information. We encourage you to read the Data Policy, and to use it to help you make informed decisions.
     
  2. Sharing Your Content and Information

    You own all of the content and information you post on Facebook, and you can control how it is shared through your privacy and application settings. In addition:
    1. For content that is covered by intellectual property rights, like photos and videos (IP content), you specifically give us the following permission, subject to your privacy and application settings: you grant us a non-exclusive, transferable, sub-licensable, royalty-free, worldwide license to use any IP content that you post on or in connection with Facebook (IP License). This IP License ends when you delete your IP content or your account unless your content has been shared with others, and they have not deleted it.
    2. When you delete IP content, it is deleted in a manner similar to emptying the recycle bin on a computer. However, you understand that removed content may persist in backup copies for a reasonable period of time (but will not be available to others).
    3. When you use an application, the application may ask for your permission to access your content and information as well as content and information that others have shared with you.  We require applications to respect your privacy, and your agreement with that application will control how the application can use, store, and transfer that content and information.  (To learn more about Platform, including how you can control what information other people may share with applications, read our Data Policy and Platform Page.)
    4. When you publish content or information using the Public setting, it means that you are allowing everyone, including people off of Facebook, to access and use that information, and to associate it with you (i.e., your name and profile picture).
    5. We always appreciate your feedback or other suggestions about Facebook, but you understand that we may use your feedback or suggestions without any obligation to compensate you for them (just as you have no obligation to offer them).
       
  3. Safety

    We do our best to keep Facebook safe, but we cannot guarantee it. We need your help to keep Facebook safe, which includes the following commitments by you:
    1. You will not post unauthorized commercial communications (such as spam) on Facebook.
    2. You will not collect users' content or information, or otherwise access Facebook, using automated means (such as harvesting bots, robots, spiders, or scrapers) without our prior permission.
    3. You will not engage in unlawful multi-level marketing, such as a pyramid scheme, on Facebook.
    4. You will not upload viruses or other malicious code.
    5. You will not solicit login information or access an account belonging to someone else.
    6. You will not bully, intimidate, or harass any user.
    7. You will not post content that: is hate speech, threatening, or pornographic; incites violence; or contains nudity or graphic or gratuitous violence.
    8. You will not develop or operate a third-party application containing alcohol-related, dating or other mature content (including advertisements) without appropriate age-based restrictions.
    9. You will not use Facebook to do anything unlawful, misleading, malicious, or discriminatory.
    10. You will not do anything that could disable, overburden, or impair the proper working or appearance of Facebook, such as a denial of service attack or interference with page rendering or other Facebook functionality.
    11. You will not facilitate or encourage any violations of this Statement or our policies.
       
  4. Registration and Account Security

    Facebook users provide their real names and information, and we need your help to keep it that way. Here are some commitments you make to us relating to registering and maintaining the security of your account:
    1. You will not provide any false personal information on Facebook, or create an account for anyone other than yourself without permission.
    2. You will not create more than one personal account.
    3. If we disable your account, you will not create another one without our permission.
    4. You will not use your personal timeline primarily for your own commercial gain, and will use a Facebook Page for such purposes.
    5. You will not use Facebook if you are under 13.
    6. You will not use Facebook if you are a convicted sex offender.
    7. You will keep your contact information accurate and up-to-date.
    8. You will not share your password (or in the case of developers, your secret key), let anyone else access your account, or do anything else that might jeopardize the security of your account.
    9. You will not transfer your account (including any Page or application you administer) to anyone without first getting our written permission.
    10. If you select a username or similar identifier for your account or Page, we reserve the right to remove or reclaim it if we believe it is appropriate (such as when a trademark owner complains about a username that does not closely relate to a user's actual name).
       
  5. Protecting Other People's Rights

    We respect other people's rights, and expect you to do the same.
    1. You will not post content or take any action on Facebook that infringes or violates someone else's rights or otherwise violates the law.
    2. We can remove any content or information you post on Facebook if we believe that it violates this Statement or our policies.
    3. We provide you with tools to help you protect your intellectual property rights. To learn more, visit our How to Report Claims of Intellectual Property Infringement page.
    4. If we remove your content for infringing someone else's copyright, and you believe we removed it by mistake, we will provide you with an opportunity to appeal.
    5. If you repeatedly infringe other people's intellectual property rights, we will disable your account when appropriate.
    6. You will not use our copyrights or Trademarks or any confusingly similar marks, except as expressly permitted by our Brand Usage Guidelines or with our prior written permission.
    7. If you collect information from users, you will: obtain their consent, make it clear you (and not Facebook) are the one collecting their information, and post a privacy policy explaining what information you collect and how you will use it.
    8. You will not post anyone's identification documents or sensitive financial information on Facebook.
    9. You will not tag users or send email invitations to non-users without their consent. Facebook offers social reporting tools to enable users to provide feedback about tagging.
       
  6. Mobile and Other Devices

    1. We currently provide our mobile services for free, but please be aware that your carrier's normal rates and fees, such as text messaging and data charges, will still apply.
    2. In the event you change or deactivate your mobile telephone number, you will update your account information on Facebook within 48 hours to ensure that your messages are not sent to the person who acquires your old number.
    3. You provide consent and all rights necessary to enable users to sync (including through an application) their devices with any information that is visible to them on Facebook.
       
  7. Payments

    If you make a payment on Facebook, you agree to our Payments Terms unless it is stated that other terms apply.
     
  8. Special Provisions Applicable to Developers/Operators of Applications and Websites 

    If you are a developer or operator of a Platform application or website or if you use Social Plugins, you must comply with the Facebook Platform Policy.
  9. About Advertisements and Other Commercial Content Served or Enhanced by Facebook

    Our goal is to deliver advertising and other commercial or sponsored content that is valuable to our users and advertisers. In order to help us do that, you agree to the following:
    1. You give us permission to use your name, profile picture, content, and information in connection with commercial, sponsored, or related content (such as a brand you like) served or enhanced by us. This means, for example, that you permit a business or other entity to pay us to display your name and/or profile picture with your content or information, without any compensation to you. If you have selected a specific audience for your content or information, we will respect your choice when we use it.
    2. We do not give your content or information to advertisers without your consent.
    3. You understand that we may not always identify paid services and communications as such.
       
  10. Special Provisions Applicable to Advertisers 

    If you use our self-service advertising creation interfaces for creation, submission and/or delivery of any advertising or other commercial or sponsored activity or content (collectively, the “Self-Serve Ad Interfaces”), you agree to our Self-Serve Ad Terms. In addition, your advertising or other commercial or sponsored activity or content placed on Facebook or our publisher network will comply with our Advertising Policies.
  11. Special Provisions Applicable to Pages

    If you create or administer a Page on Facebook, or run a promotion or an offer from your Page, you agree to our Pages Terms.
     
  12. Special Provisions Applicable to Software

    1. If you download or use our software, such as a stand-alone software product, an app, or a browser plugin, you agree that from time to time, the software may download and install upgrades, updates and additional features from us in order to improve, enhance, and further develop the software.
    2. You will not modify, create derivative works of, decompile, or otherwise attempt to extract source code from us, unless you are expressly permitted to do so under an open source license, or we give you express written permission.
  13. Amendments

    1. We’ll notify you before we make changes to these terms and give you the opportunity to review and comment on the revised terms before continuing to use our Services.
    2. If we make changes to policies, guidelines or other terms referenced in or incorporated by this Statement, we may provide notice on the Site Governance Page.
    3. Your continued use of the Facebook Services, following notice of the changes to our terms, policies or guidelines, constitutes your acceptance of our amended terms, policies or guidelines.
       
  14. Termination

    If you violate the letter or spirit of this Statement, or otherwise create risk or possible legal exposure for us, we can stop providing all or part of Facebook to you. We will notify you by email or at the next time you attempt to access your account. You may also delete your account or disable your application at any time. In all such cases, this Statement shall terminate, but the following provisions will still apply: 2.2, 2.4, 3-5, 9.3, and 14-18.
     
  15. Disputes

    1. You will resolve any claim, cause of action or dispute (claim) you have with us arising out of or relating to this Statement or Facebook exclusively in the U.S. District Court for the Northern District of California or a state court located in San Mateo County, and you agree to submit to the personal jurisdiction of such courts for the purpose of litigating all such claims. The laws of the State of California will govern this Statement, as well as any claim that might arise between you and us, without regard to conflict of law provisions.
    2. If anyone brings a claim against us related to your actions, content or information on Facebook, you will indemnify and hold us harmless from and against all damages, losses, and expenses of any kind (including reasonable legal fees and costs) related to such claim. Although we provide rules for user conduct, we do not control or direct users' actions on Facebook and are not responsible for the content or information users transmit or share on Facebook. We are not responsible for any offensive, inappropriate, obscene, unlawful or otherwise objectionable content or information you may encounter on Facebook. We are not responsible for the conduct, whether online or offline, of any user of Facebook.
    3. WE TRY TO KEEP FACEBOOK UP, BUG-FREE, AND SAFE, BUT YOU USE IT AT YOUR OWN RISK. WE ARE PROVIDING FACEBOOK AS IS WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT GUARANTEE THAT FACEBOOK WILL ALWAYS BE SAFE, SECURE OR ERROR-FREE OR THAT FACEBOOK WILL ALWAYS FUNCTION WITHOUT DISRUPTIONS, DELAYS OR IMPERFECTIONS. FACEBOOK IS NOT RESPONSIBLE FOR THE ACTIONS, CONTENT, INFORMATION, OR DATA OF THIRD PARTIES, AND YOU RELEASE US, OUR DIRECTORS, OFFICERS, EMPLOYEES, AND AGENTS FROM ANY CLAIMS AND DAMAGES, KNOWN AND UNKNOWN, ARISING OUT OF OR IN ANY WAY CONNECTED WITH ANY CLAIM YOU HAVE AGAINST ANY SUCH THIRD PARTIES. IF YOU ARE A CALIFORNIA RESIDENT, YOU WAIVE CALIFORNIA CIVIL CODE §1542, WHICH SAYS: A GENERAL RELEASE DOES NOT EXTEND TO CLAIMS WHICH THE CREDITOR DOES NOT KNOW OR SUSPECT TO EXIST IN HIS OR HER FAVOR AT THE TIME OF EXECUTING THE RELEASE, WHICH IF KNOWN BY HIM OR HER MUST HAVE MATERIALLY AFFECTED HIS OR HER SETTLEMENT WITH THE DEBTOR. WE WILL NOT BE LIABLE TO YOU FOR ANY LOST PROFITS OR OTHER CONSEQUENTIAL, SPECIAL, INDIRECT, OR INCIDENTAL DAMAGES ARISING OUT OF OR IN CONNECTION WITH THIS STATEMENT OR FACEBOOK, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. OUR AGGREGATE LIABILITY ARISING OUT OF THIS STATEMENT OR FACEBOOK WILL NOT EXCEED THE GREATER OF ONE HUNDRED DOLLARS ($100) OR THE AMOUNT YOU HAVE PAID US IN THE PAST TWELVE MONTHS. APPLICABLE LAW MAY NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY OR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. IN SUCH CASES, FACEBOOK'S LIABILITY WILL BE LIMITED TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW.
       
  16. Special Provisions Applicable to Users Outside the United States

    We strive to create a global community with consistent standards for everyone, but we also strive to respect local laws. The following provisions apply to users and non-users who interact with Facebook outside the United States:
    1. You consent to having your personal data transferred to and processed in the United States.
    2. If you are located in a country embargoed by the United States, or are on the U.S. Treasury Department's list of Specially Designated Nationals you will not engage in commercial activities on Facebook (such as advertising or payments) or operate a Platform application or website. You will not use Facebook if you are prohibited from receiving products, services, or software originating from the United States.
    3. Certain specific terms that apply only for German users are available here.
  17. Definitions

    1. By "Facebook" or” Facebook Services” we mean the features and services we make available, including through (a) our website at www.facebook.com and any other Facebook branded or co-branded websites (including sub-domains, international versions, widgets, and mobile versions); (b) our Platform; (c) social plugins such as the Like button, the Share button and other similar offerings; and (d) other media, brands, products, services, software (such as a toolbar), devices, or networks now existing or later developed. Facebook reserves the right to designate, in its sole discretion, that certain of our brands, products, or services are governed by separate terms and not this SRR.
    2. By "Platform" we mean a set of APIs and services (such as content) that enable others, including application developers and website operators, to retrieve data from Facebook or provide data to us.
    3. By "information" we mean facts and other information about you, including actions taken by users and non-users who interact with Facebook.
    4. By "content" we mean anything you or other users post, provide or share using Facebook Services.
    5. By "data" or "user data" or "user's data" we mean any data, including a user's content or information that you or third parties can retrieve from Facebook or provide to Facebook through Platform.
    6. By "post" we mean post on Facebook or otherwise make available by using Facebook.
    7. By "use" we mean use, run, copy, publicly perform or display, distribute, modify, translate, and create derivative works of.
    8. By "application" we mean any application or website that uses or accesses Platform, as well as anything else that receives or has received data from us.  If you no longer access Platform but have not deleted all data from us, the term application will apply until you delete the data.
    9. By “Trademarks” we mean the list of trademarks provided here.
       
  18. Other

    1. If you are a resident of or have your principal place of business in the US or Canada, this Statement is an agreement between you and Facebook, Inc.  Otherwise, this Statement is an agreement between you and Facebook Ireland Limited.  References to “us,” “we,” and “our” mean either Facebook, Inc. or Facebook Ireland Limited, as appropriate.
    2. This Statement makes up the entire agreement between the parties regarding Facebook, and supersedes any prior agreements.
    3. If any portion of this Statement is found to be unenforceable, the remaining portion will remain in full force and effect.
    4. If we fail to enforce any of this Statement, it will not be considered a waiver.
    5. Any amendment to or waiver of this Statement must be made in writing and signed by us.
    6. You will not transfer any of your rights or obligations under this Statement to anyone else without our consent.
    7. All of our rights and obligations under this Statement are freely assignable by us in connection with a merger, acquisition, or sale of assets, or by operation of law or otherwise.
    8. Nothing in this Statement shall prevent us from complying with the law.
    9. This Statement does not confer any third party beneficiary rights.
    10. We reserve all rights not expressly granted to you.
    11. You will comply with all applicable laws when using or accessing Facebook.

By using or accessing Facebook Services, you agree that we can collect and use such content and information in accordance with the Data Policy as amended from time to time. You may also want to review the following documents, which provide additional information about your use of Facebook:
  • Payment Terms: These additional terms apply to all payments made on or through Facebook, unless it is stated that other terms apply.
  • Platform Page: This page helps you better understand what happens when you add a third-party application or use Facebook Connect, including how they may access and use your data.
  • Facebook Platform Policies: These guidelines outline the policies that apply to applications, including Connect sites.
  • Advertising Policies: These guidelines outline the policies that apply to advertisements placed on Facebook.
  • Self-Serve Ad Terms: These terms apply when you use the Self-Serve Ad Interfaces to create, submit, or deliver any advertising or other commercial or sponsored activity or content.
  • Promotions Guidelines: These guidelines outline the policies that apply if you offer contests, sweepstakes, and other types of promotions on Facebook.
  • Facebook Brand Resources: These guidelines outline the policies that apply to use of Facebook trademarks, logos and screenshots.
  • How to Report Claims of Intellectual Property Infringement
  • Pages Terms: These guidelines apply to your use of Facebook Pages.
  • Community Standards: These guidelines outline our expectations regarding the content you post to Facebook and your activity on Facebook.
To access the Statement of Rights and Responsibilities in several different languages, change the language setting for your Facebook session by clicking on the language link in the left corner of most pages.  If the Statement is not available in the language you select, we will default to the English version.

PHP

PHP is a server-side scripting language designed primarily for web development but also used as a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the PHP reference implementation is now produced by The PHP Development Team. PHP originally stood for Personal Home Page,[4] but it now stands for the recursive acronym PHP: Hypertext Preprocessor.PHP-logo.svg
PHP code may be embedded into HTML or HTML5 markup, or it can be used in combination with various web template systems, web content management systems and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server software combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface (CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.

History

Early history

Rasmus Lerdorf (left), who wrote the original Common Gateway Interface (CGI) component, together with Andi Gutmans (middle) and Zeev Suraski (right), who rewrote the parser that formed PHP 3.
PHP development began in 1995 when Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C, which he used to maintain his personal homepage. He extended them to work with web forms and to communicate with databases, and called this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.
PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page Tools (PHP Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi on June 8, 1995. This release already had the basic functionality that PHP has as of 2013. This included Perl-like variables, form handling, and the ability to embed HTML. The syntax resembled that of Perl but was simpler, more limited and less consistent.
Lerdorf did not intend the early PHP to become a new programming language, but it grew organically, with Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any intent to write a programming language  I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way.". A development team began to form and, after months of work and beta testing, officially released PHP/FI 2 in November 1997.
The fact that PHP lacked an original overall design but instead developed organically has led to inconsistent naming of functions and inconsistent ordering of their parameters. In some cases, the function names were chosen to match the lower-level libraries which PHP was "wrapping",while in some very early versions of PHP the length of the function names was used internally as a hash function, so names were chosen to improve the distribution of hash values.

PHP 3 and 4

PHP 3.0 is the successor of PHP/FI 2.0 Zeev Suraski and Andi Gutmans rewrote the parser in 1997 and formed the base of PHP 3, changing the language's name to the recursive acronym PHP: Hypertext Preprocessor. Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski and Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in 1999. They also founded Zend Technologies in Ramat Gan, Israel.
On May 22, 2000, PHP 4, powered by the Zend Engine 1.0, was released.As of August 2008 this branch reached version 4.4.9. PHP 4 is no longer under development nor will any security updates be released.

PHP 5

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II.PHP 5 included new features such as improved support for object-oriented programming, the PHP Data Objects (PDO) extension (which defines a lightweight and consistent interface for accessing databases), and numerous performance enhancements. In 2008 PHP 5 became the only stable version under development. Late static binding had been missing from PHP and was added in version 5.3.
Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5, 2008, because of the GoPHP5 initiative, provided by a consortium of PHP developers promoting the transition from PHP 4 to PHP 5.
Over time, PHP interpreters became available on most existing 32-bit and 64-bit operating systems, either by building them from the PHP source code, or by using pre-built binaries. For the PHP versions 5.3 and 5.4, the only available Microsoft Windows binary distributions were 32-bit x86 builds, requiring Windows 32-bit compatibility mode while using Internet Information Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64 builds available for Microsoft Windows.

PHP 6 and Unicode

PHP has received criticism due to lacking native Unicode support at the core language level, instead only supporting byte strings. In 2005, a project headed by Andrei Zmievski was initiated to bring native Unicode support throughout PHP, by embedding the International Components for Unicode (ICU) library, and representing text strings as UTF-16 internally. Since this would cause major changes both to the internals of the language and to user code, it was planned to release this as version 6.0 of the language, along with other major features then in development.
However, a shortage of developers who understood the necessary changes, and performance problems arising from conversion to and from UTF-16, which is rarely used in a web context, led to delays in the project. As a result, a PHP 5.3 release was created in 2009, with many non-Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its current form was officially abandoned, and a PHP 5.4 release was prepared containing most remaining non-Unicode features from PHP 6, such as traits and closure re-binding. Initial hopes were that a new plan would be formed for Unicode integration, but as of 2014 none had been adopted.

PHP 7

During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7. The numbering of this version involved some debate. While the PHP 6 Unicode experiment had never been released, several articles and book titles referenced the PHP 6 name, which might have caused confusion if a new release were to reuse the name. After a vote, the name PHP 7 was chosen.
The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next generation (phpng). It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov, and aimed to optimize PHP performance by refactoring the Zend Engine to use more compact data structures with improved cache locality while retaining near-complete language compatibility. As of 14 July 2014, WordPress-based benchmarks, which served as the main benchmark suite for the phpng project, showed an almost 100% increase in performance. Changes from phpng are also expected to make it easier to improve performance in the future, as more compact data structures and other changes are seen as better suited for a successful migration to a just-in-time (JIT) compiler. Because of the significant changes, the reworked Zend Engine is called Zend Engine 3, succeeding Zend Engine 2 used in PHP 5.
Because of major internal changes in phpng, it must receive a new major version number of PHP, rather than a minor PHP 5 release, according to PHP's release process. Major versions of PHP are allowed to break backward-compatibility of code and therefore PHP 7 presented an opportunity for other improvements beyond phpng that require backward-compatibility breaks, including wider use of exceptions, reworking variable syntax to be more consistent and complete, and the deprecation or removal of various legacy features.
PHP 7 also introduced new language features, including return type declarations for functions, which complement the existing parameter type declarations, and support for the scalar types (integer, float, string, and boolean) in parameter and return type declarations.

PHP 8

PHP is scheduled to receive a Just In Time (JIT) compiler in its next major version.
Release history
Key
Color Meaning Development
Red Old release No development
Yellow Stable release Security fixes
Green Stable release Bug and security fixes
Blue Future release New features
Version LatestRelease date Supported until Notes
1.0 1.0.8 8 June 1995 Officially called "Personal Home Page Tools (PHP Tools)". This is the first use of the name "PHP".
2.0 2.0.1 1 November 1997 Officially called "PHP/FI 2.0". This is the first release that could actually be characterised as PHP, being a standalone language with many features that have endured to the present day.
3.0 3.0.18 6 June 1998 20 October 2000. Development moves from one person to multiple developers. Zeev Suraski and Andi Gutmans rewrite the base for this version.
4.0 4.0.6 22 May 2000 23 June 2001 Added more advanced two-stage parse/execute tag-parsing system called the Zend engine.
4.1 4.1.2 10 December 2001 12 March 2002 Introduced "superglobals" ($_GET, $_POST, $_SESSION, etc.)[56]
4.2 4.2.3 22 April 2002 6 September 2002 Disabled register_globals by default. Data received over the network is not inserted directly into the global namespace anymore, closing possible security holes in applications.
4.3 4.3.11 27 December 2002 31 March 2005 Introduced the command-line interface (CLI), to supplement the CGI.
4.4 4.4.9 11 July 2005 7 August 2008 Fixed a memory corruption bug, which required breaking binary compatibility with extensions compiled against PHP version 4.3.x.
5.0 5.0.5 13 July 2004 5 September 2005 Zend Engine II with a new object model.
5.1 5.1.6 24 November 2005 24 August 2006. Performance improvements with introduction of compiler variables in re-engineered PHP Engine. Added PHP Data Objects (PDO) as a consistent interface for accessing databases.[60]
5.2 5.2.17 2 November 2006 6 January 2011 Enabled the filter extension by default. Native JSON support.
5.3 5.3.29 30 June 2009 14 August 2014 Namespace support; late static bindings, jump label (limited goto), closures, PHP archives (phar), garbage collection for circular references, improved Windows support, sqlite3, mysqlnd as a replacement for libmysql as underlying library for the extensions that work with MySQL, fileinfo as a replacement for mime_magic for better MIME support, the Internationalization extension, and deprecation of ereg extension.
5.4 5.4.45 1 March 2012 3 September 2015 Trait support, short array syntax support. Removed items: register_globals, safe_mode, allow_call_time_pass_reference, session_register(), session_unregister() and session_is_registered(). Built-in web server. Several improvements to existing features, performance and reduced memory requirements.
5.5 5.5.38 20 June 2013 21 July 2016[55] Support for generators, finally blocks for exceptions handling, OpCache (based on Zend Optimizer+) bundled in official distribution.[62]
5.6 5.6.32 28 August 2014 31 December 2018[63] Constant scalar expressions, variadic functions, argument unpacking, new exponentiation operator, extensions of the use statement for functions and constants, new phpdbg debugger as a SAPI module, and other smaller improvements.[64]
6.x N/A Not released N/A Abandoned version of PHP that planned to include native Unicode support.[65][66]
7.0 7.0.26 3 December 2015[2] 3 December 2018[63] Zend Engine 3 (performance improvements[44] and 64-bit integer support on Windows[67]), uniform variable syntax,[49] AST-based compilation process,[68] added Closure::call(),[69] bitwise shift consistency across platforms,[70] ?? (null coalesce) operator,[71] Unicode codepoint escape sequence,[72] return type declarations,[52] scalar type (integer, float, string and boolean) declarations,[53] <=> "spaceship" three-way comparison operator,[73] generator delegation,[74] anonymous classes,[75] simpler and more consistently available CSPRNG API,[76] replacement of many remaining internal PHP "errors" with the more modern exceptions,[47] and shorthand syntax for importing multiple items from a namespace.[77]
7.1 7.1.12 1 December 2016[78][79] 1 December 2019[63] void return type,[80] class constant visibility modifiers,[81] nullable types,[82] iterable pseudo-type,[83] catching multiple exception types.[84]
7.2 7.2.0 30 November 2017[85] 30 November 2020[63] Argon2 can now be used in password functions as a secure alternative to the Bcrypt algorithm. Includes the Sodium library into the core. Argument type declarations, Object return type declarations, Parameter Type Widening, Trailing commas in list syntax
7.3 7.3.0 2018 2021 PCRE2 Migration, Trailing comma in function calls, Improved JSON error behaviour with JSON_THROW_ON_ERROR
8.0 8.0 TBA TBA
Beginning on June 28, 2011, the PHP Group implemented a timeline for the release of new versions of PHP.[46] Under this system, at least one release should occur every month. Once per year, a minor release should occur which may include new features. Every minor release should at least be supported for two years with security and bug fixes, followed by at least one year of only security fixes, for a total of a three-year release process for every minor release. No new features, unless small and self-contained, are to be introduced into a minor release during the three-year release process.
Mascot[edit]

The elePHPant, PHP mascot.
The mascot of the PHP project is the elePHPant, a blue elephant with the PHP logo on its side, designed by Vincent Pontier[86] in 1998.[87] The elePHPant is sometimes colored differently when in plush toy form.[88]
Syntax[edit]
Main article: PHP syntax and semantics
The following "Hello, World!" program is written in PHP code embedded in an HTML document:
<!DOCTYPE html>
<html>
    <head>
        <title>PHP Test</title>
    </head>
    <body>
        <?php echo '<p>Hello World</p>'; ?>
    </body>
</html>
However, as no requirement exists for PHP code to be embedded in HTML, the simplest version of Hello World may be written like this, with the closing tag omitted as preferred in files containing pure PHP code[89]
 <?="Hello World";
The PHP interpreter only executes PHP code within its delimiters. Anything outside its delimiters is not processed by PHP, although non-PHP text is still subject to control structures described in PHP code. The most common delimiters are <?php to open and ?> to close PHP sections. The shortened form <? also exists. This short delimiter makes script files less portable, since support for them can be disabled in the local PHP configuration and it is therefore discouraged.[90][91] However, there is no recommendation against the use of the echo short tag <?=.[92] Prior to PHP 5.4.0, this short syntax for echo() only works with the short_open_tag configuration setting enabled, while for PHP 5.4.0 and later it is always available.[90][93][94] The purpose of all these delimiters is to separate PHP code from non-PHP content, such as JavaScript code or HTML markup.[95]
The first form of delimiters, <?php and ?>, in XHTML and other XML documents, creates correctly formed XML processing instructions.[96] This means that the resulting mixture of PHP code and other markup in the server-side file is itself well-formed XML.
Variables are prefixed with a dollar symbol, and a type does not need to be specified in advance. PHP 5 introduced type hinting that allows functions to force their parameters to be objects of a specific class, arrays, interfaces or callback functions. However, before PHP 7.0, type hints could not be used with scalar types such as integer or string.[53]
Unlike function and class names, variable names are case sensitive. Both double-quoted ("") and heredoc strings provide the ability to interpolate a variable's value into the string.[97] PHP treats newlines as whitespace in the manner of a free-form language, and statements are terminated by a semicolon.[98] PHP has three types of comment syntax: /* */ marks block and inline comments; // as well as # are used for one-line comments.[99] The echo statement is one of several facilities PHP provides to output text, e.g., to a web browser.
In terms of keywords and language syntax, PHP is similar to the C style syntax. if conditions, for and while loops, and function returns are similar in syntax to languages such as C, C++, C#, Java and Perl.
The following is an example of PHP for loop:
<?php 
for ($x = 0; $x <= 100; $x++) {
    echo "The number is: $x <br>";
?>
Data types[edit]
PHP stores integers in a platform-dependent range, either a 64-bit or 32-bit signed integer equivalent to the C-language long type. Unsigned integers are converted to signed values in certain situations; this behavior is different from that of other programming languages.[100] Integer variables can be assigned using decimal (positive and negative), octal, hexadecimal, and binary notations.
Floating point numbers are also stored in a platform-specific range. They can be specified using floating point notation, or two forms of scientific notation.[101] PHP has a native Boolean type that is similar to the native Boolean types in Java and C++. Using the Boolean type conversion rules, non-zero values are interpreted as true and zero as false, as in Perl and C++.[101]
The null data type represents a variable that has no value; NULL is the only allowed value for this data type.[101]
Variables of the "resource" type represent references to resources from external sources. These are typically created by functions from a particular extension, and can only be processed by functions from the same extension; examples include file, image, and database resources.[101]
Arrays can contain elements of any type that PHP can handle, including resources, objects, and other arrays. Order is preserved in lists of values and in hashes with both keys and values, and the two can be intermingled.[101] PHP also supports strings, which can be used with single quotes, double quotes, nowdoc or heredoc syntax.[102]
The Standard PHP Library (SPL) attempts to solve standard problems and implements efficient data access interfaces and classes.[103]
Functions[edit]
PHP defines a large array of functions in the core language and many are also available in various extensions; these functions are well documented in the online PHP documentation.[104] However, the built-in library has a wide variety of naming conventions and associated inconsistencies, as described under history above.
Custom functions may be defined by the developer, e.g.:
function myAge($birthYear) {                                  // defines a function, this one is named "myAge"
    $yearsOld = date('Y') - $birthYear;                       // calculates the age
    return $yearsOld . ' year' . ($yearsOld != 1 ? 's' : ''); // returns the age in a descriptive form
}

echo 'I am currently ' . myAge(1981) . ' old.';               // outputs the text concatenated
                                                              // with the return value of myAge()
// As the result of this syntax, myAge() is called.
In 2017, the output of the above sample program is 'I am currently 36 years old.'
In lieu of function pointers, functions in PHP can be referenced by a string containing their name. In this manner, normal PHP functions can be used, for example, as callbacks or within function tables.[105] User-defined functions may be created at any time without being prototyped.[104][105] Functions may be defined inside code blocks, permitting a run-time decision as to whether or not a function should be defined. There is a function_exists function that determines whether a function with a given name has already been defined. Function calls must use parentheses, with the exception of zero-argument class constructor functions called with the PHP operator new, in which case parentheses are optional.
Until PHP 5.3, support for anonymous functions and closures did not exist in PHP. While create_function() exists since PHP 4.0.1, it is merely a thin wrapper around eval() that allows normal PHP functions to be created during program execution.[106] PHP 5.3 added syntax to define an anonymous function or "closure"[107] which can capture variables from the surrounding scope:
function getAdder($x) {
    return function($y) use ($x) {
        return $x + $y;
    };
}

$adder = getAdder(8);
echo $adder(2); // prints "10"
In the example above, getAdder() function creates a closure using passed argument $x (the keyword use imports a variable from the lexical context), which takes an additional argument $y, and returns the created closure to the caller. Such a function is a first-class object, meaning that it can be stored in a variable, passed as a parameter to other functions, etc.[108]
Unusually for a dynamically typed language, PHP supports type declarations on function parameters, which are enforced at runtime. This has been supported for classes and interfaces since PHP 5.0, for arrays since PHP 5.1, for "callables" since PHP 5.4, and scalar (integer, float, string and boolean) types since PHP 7.0.[53] PHP 7.0 also has type declarations for function return types, expressed by placing the type name after the list of parameters, preceded by a colon.[52] For example, the getAdder function from the earlier example could be annotated with types like so in PHP 7:
function getAdder(int $x): \Closure {
    return function(int $y) use ($x) : int {
        return $x + $y;
    };
}

$adder = getAdder(8);
echo $adder(2);        // prints "10"
echo $adder(null);     // throws an exception because an incorrect type was passed
$adder = getAdder([]); // would also throw an exception
By default, scalar type declarations follow weak typing principles. So, for example, if a parameter's type is int, PHP would allow not only integers, but also convertible numeric strings, floats or booleans to be passed to that function, and would convert them.[53] However, PHP 7 has a "strict typing" mode which, when used, disallows such conversions for function calls and returns within a file.[53]
Object-oriented programming[edit]
Basic object-oriented programming functionality was added in PHP 3 and improved in PHP 4.[5] This allowed for PHP to gain further abstraction, making creative tasks easier for programmers using the language. Object handling was completely rewritten for PHP 5, expanding the feature set and enhancing performance.[109] In previous versions of PHP, objects were handled like value types.[109] The drawback of this method was that code had to make heavy use of PHP's "reference" variables if it wanted to modify an object it was passed rather than creating a copy of it. In the new approach, objects are referenced by handle, and not by value.
PHP 5 introduced private and protected member variables and methods, along with abstract classes, final classes, abstract methods, and final methods. It also introduced a standard way of declaring constructors and destructors, similar to that of other object-oriented languages such as C++, and a standard exception handling model. Furthermore, PHP 5 added interfaces and allowed for multiple interfaces to be implemented. There are special interfaces that allow objects to interact with the runtime system. Objects implementing ArrayAccess can be used with array syntax and objects implementing Iterator or IteratorAggregate can be used with the foreach language construct. There is no virtual table feature in the engine, so static variables are bound with a name instead of a reference at compile time.[110]
If the developer creates a copy of an object using the reserved word clone, the Zend engine will check whether a __clone() method has been defined. If not, it will call a default __clone() which will copy the object's properties. If a __clone() method is defined, then it will be responsible for setting the necessary properties in the created object. For convenience, the engine will supply a function that imports the properties of the source object, so the programmer can start with a by-value replica of the source object and only override properties that need to be changed.[111]
The following is a basic example of object-oriented programming in PHP:
class Person
{
    public $firstName;
    public $lastName;

    public function __construct(string $firstName, string $lastName = '') { // optional second argument
        $this->firstName = $firstName;
        $this->lastName  = $lastName;
    }

    public function greet(): string {
        return 'Hello, my name is ' . $this->firstName .
               (($this->lastName != '') ? (' ' . $this->lastName) : '') . '.';
    }

    public static function staticGreet(string $firstName, string $lastName) {
        return 'Hello, my name is ' . $firstName . ' ' . $lastName . '.';
    }
}

$he    = new Person('John', 'Smith');
$she   = new Person('Sally', 'Davis');
$other = new Person('iAmine');

echo $he->greet(); // prints "Hello, my name is John Smith."
echo '<br />';

echo $she->greet(); // prints "Hello, my name is Sally Davis."
echo '<br />';

echo $other->greet(); // prints "Hello, my name is iAmine."
echo '<br />';

echo Person::staticGreet('Jane', 'Doe'); // prints "Hello, my name is Jane Doe."
The visibility of PHP properties and methods is defined using the keywords public, private, and protected. The default is public, if only var is used; var is a synonym for public. Items declared public can be accessed everywhere. protected limits access to inherited classes (and to the class that defines the item). private limits visibility only to the class that defines the item.[112] Objects of the same type have access to each other's private and protected members even though they are not the same instance. PHP's member visibility features have sometimes been described as "highly useful."[113] However, they have also sometimes been described as "at best irrelevant and at worst positively harmful."[114]
Implementations[edit]
The original, only complete and most widely used PHP implementation is powered by the Zend Engine and known simply as PHP. To disambiguate it from other implementations, it is sometimes unofficially referred to as "Zend PHP". The Zend Engine compiles PHP source code on-the-fly into an internal format that it can execute, thus it works as an interpreter.[115][116] It is also the "reference implementation" of PHP, as PHP has no formal specification, and so the semantics of Zend PHP define the semantics of PHP itself. Due to the complex and nuanced semantics of PHP, defined by how Zend works, it is difficult for competing implementations to offer complete compatibility.
PHP's single-request-per-script-execution model, and the fact that the Zend Engine is an interpreter, leads to inefficiency; as a result, various products have been developed to help improve PHP performance. In order to speed up execution time and not have to compile the PHP source code every time the web page is accessed, PHP scripts can also be deployed in the PHP engine's internal format by using an opcode cache, which works by caching the compiled form of a PHP script (opcodes) in shared memory to avoid the overhead of parsing and compiling the code every time the script runs. An opcode cache, Zend Opcache, is built into PHP since version 5.5.[117] Another example of a widely used opcode cache is the Alternative PHP Cache (APC), which is available as a PECL extension.[118]
While Zend PHP is still the most popular implementation, several other implementations have been developed. Some of these are compilers or support JIT compilation, and hence offer performance benefits over Zend PHP at the expense of lacking full PHP compatibility. Alternative implementations include the following:
HipHop Virtual Machine (HHVM) – developed at Facebook and available as open source, it converts PHP code into a high-level bytecode (commonly known as an intermediate language), which is then translated into x86-64 machine code dynamically at runtime by a just-in-time (JIT) compiler, resulting in up to 6× performance improvements.[119]
Parrot – a virtual machine designed to run dynamic languages efficiently; Pipp transforms the PHP source code into the Parrot intermediate representation, which is then translated into the Parrot's bytecode and executed by the virtual machine.
Phalanger – compiles PHP into Common Intermediate Language (CIL) bytecode
HipHop – developed at Facebook and available as open source, it transforms the PHP scripts into C++ code and then compiles the resulting code, reducing the server load up to 50%. In early 2013, Facebook deprecated it in favor of HHVM due to multiple reasons, including deployment difficulties and lack of support for the whole PHP language, including the create_function() and eval() constructs.[120]
Licensing[edit]
PHP is free software released under the PHP License, which stipulates that:[121]
Products derived from this software may not be called "PHP", nor may "PHP" appear in their name, without prior written permission from group@php.net. You may indicate that your software works in conjunction with PHP by saying "Foo for PHP" instead of calling it "PHP Foo" or "phpfoo".
This restriction on use of "PHP" makes the PHP License incompatible with the General Public License (GPL), while the Zend License is incompatible due to an advertising clause similar to that of the original BSD license.[122]
Development and community[edit]
PHP includes various free and open-source libraries in its source distribution, or uses them in resulting PHP binary builds. PHP is fundamentally an Internet-aware system with built-in modules for accessing File Transfer Protocol (FTP) servers and many database servers, including PostgreSQL, MySQL, Microsoft SQL Server and SQLite (which is an embedded database), LDAP servers, and others. Numerous functions familiar to C programmers, such as those in the stdio family, are available in standard PHP builds.[123]
PHP allows developers to write extensions in C to add functionality to the PHP language. PHP extensions can be compiled statically into PHP or loaded dynamically at runtime. Numerous extensions have been written to add support for the Windows API, process management on Unix-like operating systems, multibyte strings (Unicode), cURL, and several popular compression formats. Other PHP features made available through extensions include integration with IRC, dynamic generation of images and Adobe Flash content, PHP Data Objects (PDO) as an abstraction layer used for accessing databases,[124][125][126][127][128][129][130] and even speech synthesis. Some of the language's core functions, such as those dealing with strings and arrays, are also implemented as extensions.[131] The PHP Extension Community Library (PECL) project is a repository for extensions to the PHP language.[132]
Some other projects, such as Zephir, provide the ability for PHP extensions to be created in a high-level language and compiled into native PHP extensions. Such an approach, instead of writing PHP extensions directly in C, simplifies the development of extensions and reduces the time required for programming and testing.[133]
The PHP Group consists of ten people (as of 2015): Thies C. Arntzen, Stig Bakken, Shane Caraveo, Andi Gutmans, Rasmus Lerdorf, Sam Ruby, Sascha Schumann, Zeev Suraski, Jim Winstead, Andrei Zmievski.[134]
Zend Technologies provides a PHP Certification based on PHP 5.5[135] exam for programmers to become certified PHP developers.
Installation and configuration[edit]
There are two primary ways for adding support for PHP to a web server – as a native web server module, or as a CGI executable. PHP has a direct module interface called Server Application Programming Interface (SAPI), which is supported by many web servers including Apache HTTP Server, Microsoft IIS, Netscape (now defunct) and iPlanet. Some other web servers, such as OmniHTTPd, support the Internet Server Application Programming Interface (ISAPI), which is a Microsoft's web server module interface. If PHP has no module support for a web server, it can always be used as a Common Gateway Interface (CGI) or FastCGI processor; in that case, the web server is configured to use PHP's CGI executable to process all requests to PHP files.[136]
PHP-FPM (FastCGI Process Manager) is an alternative FastCGI implementation for PHP, bundled with the official PHP distribution since version 5.3.3.[137] When compared to the older FastCGI implementation, it contains some additional features, mostly useful for heavily loaded web servers.[138]
When using PHP for command-line scripting, a PHP command-line interface (CLI) executable is needed. PHP supports a CLI SAPI as of PHP 4.3.0.[139] The main focus of this SAPI is developing shell applications using PHP. There are quite a few differences between the CLI SAPI and other SAPIs, although they do share many of the same behaviors.[140]
PHP has a direct module interface called SAPI for different web servers;[141] in case of PHP 5 and Apache 2.0 on Windows, it is provided in form of a DLL file called php5apache2.dll,[142] which is a module that, among other functions, provides an interface between PHP and the web server, implemented in a form that the server understands. This form is what is known as a SAPI.
There are different kinds of SAPIs for various web server extensions. For example, in addition to those listed above, other SAPIs for the PHP language include the Common Gateway Interface (CGI) and command-line interface (CLI).[141][143]
PHP can also be used for writing desktop graphical user interface (GUI) applications, by using the PHP-GTK extension. PHP-GTK is not included in the official PHP distribution,[136] and as an extension it can be used only with PHP versions 5.1.0 and newer. The most common way of installing PHP-GTK is compiling it from the source code.[144]
When PHP is installed and used in cloud environments, software development kits (SDKs) are provided for using cloud-specific features. For example:
Amazon Web Services provides the AWS SDK for PHP[145]
Windows Azure can be used with the Windows Azure SDK for PHP.[146]
Numerous configuration options are supported, affecting both core PHP features and extensions.[147][148] Configuration file php.ini is searched for in different locations, depending on the way PHP is used.[149] The configuration file is split into various sections,[150] while some of the configuration options can be also set within the web server configuration.[151]
Use[edit]

A broad overview of the LAMP software bundle, displayed here together with Squid.
PHP is a general-purpose scripting language that is especially suited to server-side web development, in which case PHP generally runs on a web server. Any PHP code in a requested file is executed by the PHP runtime, usually to create dynamic web page content or dynamic images used on websites or elsewhere.[152] It can also be used for command-line scripting and client-side graphical user interface (GUI) applications. PHP can be deployed on most web servers, many operating systems and platforms, and can be used with many relational database management systems (RDBMS). Most web hosting providers support PHP for use by their clients. It is available free of charge, and the PHP Group provides the complete source code for users to build, customize and extend for their own use.[8]

Dynamic web page: example of server-side scripting (PHP and MySQL).
PHP acts primarily as a filter,[153] taking input from a file or stream containing text and/or PHP instructions and outputting another stream of data. Most commonly the output will be HTML, although it could be JSON, XML or binary data such as image or audio formats. Since PHP 4, the PHP parser compiles input to produce bytecode for processing by the Zend Engine, giving improved performance over its interpreter predecessor.[154]
Originally designed to create dynamic web pages, PHP now focuses mainly on server-side scripting,[155] and it is similar to other server-side scripting languages that provide dynamic content from a web server to a client, such as Microsoft's Classic ASP, Sun Microsystems' JavaServer Pages,[156] and mod_perl. PHP has also attracted the development of many software frameworks that provide building blocks and a design structure to promote rapid application development (RAD). Some of these include PRADO, CakePHP, Symfony, CodeIgniter, Laravel, Yii Framework, Phalcon and Zend Framework, offering features similar to other web frameworks.
The LAMP architecture has become popular in the web industry as a way of deploying web applications.[157] PHP is commonly used as the P in this bundle alongside Linux, Apache and MySQL, although the P may also refer to Python, Perl, or some mix of the three. Similar packages, WAMP and MAMP, are also available for Windows and macOS, with the first letter standing for the respective operating system. Although both PHP and Apache are provided as part of the macOS base install, users of these packages seek a simpler installation mechanism that can be more easily kept up to date.
As of April 2007, over 20 million Internet domains had web services hosted on servers with PHP installed and mod_php was recorded as the most popular Apache HTTP Server module.[158] As of May 2017, PHP was used as the server-side programming language on 83% of 10 million most popular websites.[159] Web content management systems written in PHP include MediaWiki,[160] Joomla,[161] eZ Publish, eZ Platform, SilverStripe,[162] WordPress,[163] Drupal,[164] and Moodle.[165] Websites written in PHP, in back-end and/or user-facing portion, include Facebook,[166] Digg,[167] Tumblr,[168] Dailymotion,[169] and Slack.[170]
For specific and more advanced usage scenarios, PHP offers a well defined and documented way for writing custom extensions in C or C++.[171][172][173][174][175][176][177] Besides extending the language itself in form of additional libraries, extensions are providing a way for improving execution speed where it is critical and there is room for improvements by using a true compiled language.[178][179] PHP also offers well defined ways for embedding itself into other software projects. That way PHP can be easily used as an internal scripting language for another project, also providing tight interfacing with the project's specific internal data structures.[180]
PHP received mixed reviews due to lacking support for multithreading at the core language level,[181] though using threads is made possible by the "pthreads" PECL extension.[182][183]
As of January 2013, PHP was used in more than 240 million websites (39% of those sampled) and was installed on 2.1 million web servers.[184]
Security[edit]
In 2013, 9% of all vulnerabilities listed by the National Vulnerability Database were linked to PHP;[185] historically, about 30% of all vulnerabilities listed since 1996 in this database are linked to PHP. Technical security flaws of the language itself or of its core libraries are not frequent (these numbered 22 in 2009, which was about 1% of the total, although PHP applies to about 20% of programs listed.)[186] Recognizing that programmers make mistakes, some languages include taint checking to automatically detect the lack of input validation which induces many issues. Such a feature is being developed for PHP,[187] but its inclusion into a release has been rejected several times in the past.[188][189]
There are advanced protection patches, such as Suhosin and Hardening-Patch, that are especially designed for web hosting environments,[190] primarily due to these environments being seen as places where carelessly written code may run.
There are certain language features and configuration parameters (primarily the default values for such runtime settings) that make PHP applications prone to security issues. Among these, magic_quotes_gpc and register_globals[191] configuration directives are the best known; the latter made any URL parameters become PHP variables, opening a path for serious security vulnerabilities by allowing an attacker to set the value of any uninitialized global variable and interfere with the execution of a PHP script. Support for "magic quotes" and "register globals" has been deprecated as of PHP 5.3.0, and removed as of PHP 5.4.0.[192]
Another example for the runtime settings vulnerability comes from failing to disable PHP execution (via engine configuration directive)[193] for the directory where uploaded images are stored; leaving the default settings can result in execution of malicious PHP code embedded within the uploaded images.[194][195][196] Also, leaving enabled the dynamic loading of PHP extensions (via enable_dl configuration directive)[197] in a shared web hosting environment can lead to security issues.[198][199]
Also, implied type conversions that result in incompatible values being treated as identical against the programmer's intent can lead to security issues. For example, the result of the comparison "0e1234" == "0" comparison is true because the first compared value is treated as scientific notation having the value (0×101234), i.e. zero. This feature resulted in authentication vulnerabilities in Simple Machines Forum,[200] Typo3[201] and phpBB[202] when MD5 password hashes were compared. Instead, either the function strcmp or the identity operator (===) should be used; "0e1234" === "0" results in false.[203]
In a 2013 analysis of over 170,000 website defacements, published by Zone-H, the most frequently (53%) used technique was exploitation of file inclusion vulnerability, mostly related to insecure usage of the PHP functions include, require, and allow_url_fopen.[204][205]
Criticism[edit]
Despite being a programming language that powers 80% of the web[206], PHP has faced a lots of criticism. PHP has been criticized for many reasons, the most common reasons have always been not being strictly type cast and lacking high scalability. Many languages have been predicted to replace PHP in past, but the user base of PHP is still considerably large as of 2017. Despite all the criticism, PHP has outlived the expectation of many[207] and is used by some of the most famous CMSs like Wordpress and frameworks like Laravel. The reason for this is considered regular developments that have been done in PHP that have matured PHP as a programming language to be very easy to design, develop and deploy.[citation needed]

RAM

Alternatively referred to as main memory, primary memory, or system memory, Random Access Memory (RAM) is a hardware device that allows information to be stored and retrieved on a computer. RAM is usually associated with DRAM, which is a type of memory module. Because information is accessed randomly instead of sequentially like it is on a CD or hard drive, the computer can access the data much faster. However, unlike ROM or the hard drive, RAM is a volatile memory and requires power to keep the data accessible. If the computer is turned off, all data contained in RAM is lost.

Tip: New users often confuse RAM with disk drive space. See our memory definition for a comparison between memory and storage.

Types of RAM

Over the evolution of the computer there have been different variations of RAM. Some of the more common examples are DIMM, RIMM, SIMM, SO-DIMM, and SOO-RIMM. Below is an example image of a 512 MB DIMM computer memory module, a typical piece of RAM found in desktop computers. This memory module would be installed into one of the memory slots on a motherboard.

Computer DIMM or dual-inline memory module

Additional RAM information

As the computer boots, parts of the operating system and drivers are loaded into memory, which allows the CPU to process the instructions faster and speeds up the boot process. After the operating system has loaded, each program you open, such as the browser you're using to view this page, is loaded into memory while it is running. If too many programs are open the computer will swap the data in the memory between the RAM and the hard disk drive.

History of RAM

The first form of RAM came about in 1947 with the use of the Williams tube. It utilized a cathode ray tube (CRT) and data was stored on the face of the CRT as electrically charged spots.

The second widely used form of RAM was magnetic-core memory, invented in 1947. Frederick Viehe is credited with much of the work, having filed for several patents relating to the design. Magnetic-core memory works through the use of tiny metal rings and wires connecting to each ring. One bit of data could be stored per ring and accessed at any time.

However, RAM as we know it today, as solid-state memory, was first invented in 1968 by Robert Dennard. Known specifically as dynamic random access memory, or DRAM, transistors were used to store bits of data