Zend\Mail 2.3 from IMAPd because it’s buggy as hell. I think the programmers of a big framework like Zend Framework have more responsibility than others. But if I like to release such a buggy software like
Zend\Mail I only would do that as a beta-status. Like the situation is with IMPAd. IMAPd isn’t in a production stage because not all specifications of RFC 3501 are implemented yet. And maybe no all specifications ever will be implemented. But who knows? However, IMAPd is only in beta stage. The version number 0.2.0 also confirms that fact. If you know Semantic Versioning 0.2.0 means that it’s not a full-version release. And so I would do it with
Zend\Mail. The version 2.3 of
Zend\Mail says that somebody rewrote the API - twice. And if a trash software like
Zend\Mail is still crap after the second time, I for my part as a coder would kill myself for producing such piece of shit of a code before releasing this to the wild. The Zend Framework is not a high-quality product. I know that everybody makes mistakes, but
Zend\Mail seems that it has not even be tested. As you can see I submitted Issue 6317 to the Zend Frameworks GitHub project page. If you have the choice to avoid the Zend Framework avoid it. Unfortunately I have not removed 100% of the Zend Framework. Some constants are still used. And also
Zend\Mail\Message is used by IMAPd 0.2.0.
I can’t retrace that some coders are not producing high-quality codes. If it comes to programming and big products used by thousands of users you can’t be vague. The main obligation of big frameworks should be to produce high-quality products for end-users like me. Even if it’s Open Source and you don’t make any money with it. But it seems that the coders of frameworks are looking for quantity, not for quality. It’s in general a deficit that nobody would like to produce high-quality codes. I don’t know why.