That Podcast, hosted by PHP community members Beau Simensen and Dave Marshall, has posted their latest episode - Episode #41: SAD.

Beau and Dave talk about PHP-FIG, an intersection of health and technology, Symfony and bitcoin bots.

Other topics mentioned in this latest show include:

• the article "Minimal HTTP middleware"
• SAD lamps
• the Symfony service locator in v3.3
• the park.io domain name backordering service

You can listen to this latest episode either using the in-page audio player or by downloading the show for listening at your leisure. If you enjoy the show and aren't already subscribed, be sure to add their feed to your reader and follow them on Twitter for updates when new shows are released.

Michael Kimsal has posted some more thoughts on what he calls the "sad state of PHP development" pointing out some of the practices of the PHP group surrounding the development of the language.

Every few months there’s a release, whether large or small, which introduces new features and bug fixes. However, with every release also comes fears of tiny, sometimes undocumented, changes that break existing code, and often for no solid reason other than someone with commit access decided they liked the ‘new’ way better than the old way.

He points out a specific example, get_object_vars and how its return values were changed in an earlier release as well as the update to glob made recently to change its return types.

In his opinion:

No changes should be made to the PHP core without an issue being opened, either in the 'bug' tracker or some other issues tracker.

Be sure to check out the comments for other great opinions on the topic.

Michael Kimsal has posted some more thoughts on what he calls the "sad state of PHP development" pointing out some of the practices of the PHP group surrounding the development of the language.

Every few months there’s a release, whether large or small, which introduces new features and bug fixes. However, with every release also comes fears of tiny, sometimes undocumented, changes that break existing code, and often for no solid reason other than someone with commit access decided they liked the ‘new’ way better than the old way.

He points out a specific example, get_object_vars and how its return values were changed in an earlier release as well as the update to glob made recently to change its return types.

In his opinion:

No changes should be made to the PHP core without an issue being opened, either in the 'bug' tracker or some other issues tracker.

Be sure to check out the comments for other great opinions on the topic.

Never let it be said that geeks aren't without a sense of humor - even the saddest moments seem somewhat happer when expressed through code.

A sad poem of an algorithm where solitude brought excessive use of cpu cycles and memory allocation for redundant data (it copied over and over again the same image till all memory was filled with it)

This definitely belongs in the "random PHP-related things" area, but it's still a fun little read. Check it out - just try to not get too despondent.

Never let it be said that geeks aren't without a sense of humor - even the saddest moments seem somewhat happer when expressed through code.

A sad poem of an algorithm where solitude brought excessive use of cpu cycles and memory allocation for redundant data (it copied over and over again the same image till all memory was filled with it)

This definitely belongs in the "random PHP-related things" area, but it's still a fun little read. Check it out - just try to not get too despondent.