Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Dylan Bridgman:
Improving perceived load time
Aug 06, 2015 @ 09:43:34

On Medium.com Dylan Bridgman has posted a tutorial with a few tips helping you improve the perceived load time of your application, the time between when the page starts loading and the user can first do something with its contents.

In this article I will concentrate on perceived load time. That is the time from when a page starts loading until the user is able to proceed. There have been other articles on this topic, some of which go into far more detail in some areas. My intention is to give a summary on the latest information and what you should be doing in PHP. I will link to additional information where applicable.

He breaks the advice up into three main categories: output buffering, multiple connections and using correctly structured pages. Under each section there's a few sub-points with more information, details on implementation and links to other additional information. He also includes an example that combines all of the advice into one PHP/HTML script outputting some basic content.

tagged: perceived load time tutorial outputbuffer thread structure

Link: https://medium.com/@dylanbr/improving-perceived-load-time-a83aa32851b0

Padraic Brady's Blog:
To PEAR or not to PEAR? And how to PEAR anyway?
Oct 24, 2007 @ 08:04:00

In his latest post, Padraic Brady takes a look at PEAR in a verb form - both in how you can use it and what sorts of things it has in store.

over the last few months after finally getting over my ignorance of PEAR beyond it being a hodge podge of packages of dubious quality I've been questioning whether pearifying my future and past code is worthwhile. The answer is a resounding YES.

Unfortunately, there are some barriers for most people to get into the PEAR world (including the lack of the "coolest packages") with some of the perceived barriers including:

  • PEAR will require large scale changes to my shiny new cool code
  • PEAR only allows proposals for complete functional code
  • PEAR is elitist
  • PEAR is fossilised

He also talks about PEAR packages and dispels one of the most popular myths about the package repository - "you can't use PEAR on a shared host".

tagged: pear package perceived barrier repository pear package perceived barrier repository

Link:

Padraic Brady's Blog:
To PEAR or not to PEAR? And how to PEAR anyway?
Oct 24, 2007 @ 08:04:00

In his latest post, Padraic Brady takes a look at PEAR in a verb form - both in how you can use it and what sorts of things it has in store.

over the last few months after finally getting over my ignorance of PEAR beyond it being a hodge podge of packages of dubious quality I've been questioning whether pearifying my future and past code is worthwhile. The answer is a resounding YES.

Unfortunately, there are some barriers for most people to get into the PEAR world (including the lack of the "coolest packages") with some of the perceived barriers including:

  • PEAR will require large scale changes to my shiny new cool code
  • PEAR only allows proposals for complete functional code
  • PEAR is elitist
  • PEAR is fossilised

He also talks about PEAR packages and dispels one of the most popular myths about the package repository - "you can't use PEAR on a shared host".

tagged: pear package perceived barrier repository pear package perceived barrier repository

Link: