So, we're on to 5.3.10, to fix a bug introduced by 5.3.9.
While I understand why 5.3.9 was necessary, I feel more than a little bit disconcerted that 5.3.10 was needed so soon because of a problem introduced by 5.3.9 - especially the nuclear grade vulnerability that was introduced as a consequence (5.3.9 introduces an arbitrary remote code execution vuln)
I think half the problem is that they're pushing towards 5.4 and they're trying to push the language to grow up and shake off some of its heritage but the really disconcerting thing is that - behind the scenes - it's looking more and more like the SMF crapshoot did: more and more of the essentially-volunteer devs are stepping back and some features are being shouted down for little good reason, and more than one capable developer has withdrawn themselves from being part of the 'core' because of their views on the politics.
While I understand why 5.3.9 was necessary, I feel more than a little bit disconcerted that 5.3.10 was needed so soon because of a problem introduced by 5.3.9 - especially the nuclear grade vulnerability that was introduced as a consequence (5.3.9 introduces an arbitrary remote code execution vuln)
I think half the problem is that they're pushing towards 5.4 and they're trying to push the language to grow up and shake off some of its heritage but the really disconcerting thing is that - behind the scenes - it's looking more and more like the SMF crapshoot did: more and more of the essentially-volunteer devs are stepping back and some features are being shouted down for little good reason, and more than one capable developer has withdrawn themselves from being part of the 'core' because of their views on the politics.


