See My current HTML boilerplate for some good ideas for a starting place for HTML content. I kept a copy, here.
A logical way to test online software
An interesting approach to testing web services: A logical way to test online software.
Firefox 88
A new version of Firefox released: Firefox 88.
How often do people actually copy and paste from Stack Overflow?
How the Axiom of Choice Gives Sizeless Sets
How the Axiom of Choice Gives Sizeless Sets | Infinite Series. “The size of the set can’t be zero and it can’t be non zero.” Figures.
PHP in 2021
A nice write up on PHP’s recent successes: PHP in 2021.
PHP prepared statements and stored procedures
Here’s some good documentation on PHP prepared statements and stored procedures including how to call stored procedures with output parameters.
Installing zstd lib for PHP
To get the zstd_compress PHP function:
# apt install php7.2-dev # pecl install zstd
Then add “extension=zstd.so” to php.ini.
The Architecture Behind A One-Person Tech Startup
This on HN today: The Architecture Behind A One-Person Tech Startup.
Do you need to call PDOStatement::closeCursor when you’re done with the statement?
The answer is no, so long as you’re not preparing to execute the statement again. I figured this out by looking at the code for PDOStatement::closeCursor and the MySQL implementation. Seems to me that all the freeing necessary is done in the destructor so if you’re not planning to use the statement again it seems to me that you can safely omit the call to PDOStatement::closeCursor(). On the other hand if you are going to reuse the statement calling closeCursor seems like it’s a pretty important thing to do. It would be nice if PDOStatement::fetchAll() called closeCursor() for us, but I don’t think it does.