Post by 10 Things Not to Do in PHP 7 on Dec 26, 2023 16:38:16 GMT 6.5
What Not to Do in PHP 7 Don't Use mysql_ Functions Don't Write Superfluous Code Don't Use PHP Closing Tags Do Not Pass By Reference If It Is Not Necessary Don't Run Query in a Loop Do not use * in SQL queries Do Not Trust User Input Don't Try to Be Too Good Don't Reinvent the Wheel Don't Neglect Other Languages 1. Don't Use mysql_ Functions The time has finally come when you won't just be advised to stop using the features mysql_. PHP 7 will remove them from the core entirely, meaning you'll have to switch to the mysqli_much better functions or the even more flexible PDO implementation. 2. Don't Write Superfluous Code This may seem like a simple thing, but it will become increasingly important because speed increases in PHP 7 can hide some of your problems.
Don't be satisfied with the speed of your site simply because switching to Buy Bulk SMS Service PHP 7 made it faster. To understand how important speed is and what you can do to improve things, take a look at our introductory guide to optimizing speed. As a developer you should always make sure to load scripts only when they are needed, chain them when possible, write efficient database queries, use caching when possible, and so on. To give a quick boost to overall optimization, you can also minify your code. Kinsta has integrated a code minification feature right into the MyKinsta dashboard : this allows customers to enable automatic minification of CSS and JavaScript with a simple click. 3. Don't Use PHP Closing Tags If you take a look, most WordPress core files omit the trailing PHP tag when a file ends with PHP code. In fact, the Zend Framework expressly prohibits this .
It is not required by PHP and omitting it at the end of a file ensures that trailing whitespace cannot be added. 4. Don't Go By Reference If It Is Not Necessary Personally I don't like to go by reference. I understand that in some cases it is useful, but in many others it makes the code harder to understand and follow and above all it makes the result difficult to predict. Apparently, people think this makes their code faster, which, according to experienced PHP programmers , is not true. An example of why references are not a good thing are native functions shuffle()and sort(). Instead of returning a shuffled or sorted array, they modify the original, which to me is completely illogical. 5. Don't Run Queries in a Loop Running database queries in a loop is just a waste. It puts unnecessary strain on your systems, and chances are you can get the same result faster outside the loop.
Don't be satisfied with the speed of your site simply because switching to Buy Bulk SMS Service PHP 7 made it faster. To understand how important speed is and what you can do to improve things, take a look at our introductory guide to optimizing speed. As a developer you should always make sure to load scripts only when they are needed, chain them when possible, write efficient database queries, use caching when possible, and so on. To give a quick boost to overall optimization, you can also minify your code. Kinsta has integrated a code minification feature right into the MyKinsta dashboard : this allows customers to enable automatic minification of CSS and JavaScript with a simple click. 3. Don't Use PHP Closing Tags If you take a look, most WordPress core files omit the trailing PHP tag when a file ends with PHP code. In fact, the Zend Framework expressly prohibits this .
It is not required by PHP and omitting it at the end of a file ensures that trailing whitespace cannot be added. 4. Don't Go By Reference If It Is Not Necessary Personally I don't like to go by reference. I understand that in some cases it is useful, but in many others it makes the code harder to understand and follow and above all it makes the result difficult to predict. Apparently, people think this makes their code faster, which, according to experienced PHP programmers , is not true. An example of why references are not a good thing are native functions shuffle()and sort(). Instead of returning a shuffled or sorted array, they modify the original, which to me is completely illogical. 5. Don't Run Queries in a Loop Running database queries in a loop is just a waste. It puts unnecessary strain on your systems, and chances are you can get the same result faster outside the loop.