3 ms·
meh. it's opt-in to downgrade security. so typos, wrong data, etc would keep the good safety. it's backward compatible. and above all, if you really cared yo
by gcb0 11y ago
meh.
it's opt-in to downgrade security. so typos, wrong data, etc would keep the good safety.
it's backward compatible.
and above all, if you really cared you would have written at least a decent use case that actually serialized a single class and submitted to places the dev look, like the several anonymous forms on the site.
php is the most convenient project to send bugs to. zero logins. but you choose reddit and hacker news
- thrownear 11y ago>it's opt-in to downgrade security. so typos, wrong data, etc would keep the good safety... Not sure I follow. Please explain. >if you really cared you would have written at least a decent us.. And the point is not about fixing this issue. The point is to show that the php development is still follows the same path that it has been following since the beginning. The same path that resulted in so many weird behaviors and pit falls. I don't see any reason why the language can be thought as 'improving'. As claimed by legions of php users. Please note that I don't consider simply increasing the feature count of the language as 'improving'. >php is the most convenient project to send bugs to. zero logins. but you choose reddit and hacker news I really don't care about improving the language because I don't think it is possible. It is a lost cause. The only think that can be done is to spread awareness of its gross inferiority.