3 ms·
>Respectfully, if you can't read the code, you're not really entitled to have opinions about it. I disagree. That is like saying if you can't read or write Eng
by nivla 13y ago
>Respectfully, if you can't read the code, you're not really entitled to have opinions about it.
I disagree. That is like saying if you can't read or write English, you shouldn't have a say in a law that affects you. I bet 90% of the users here don't know how MD5 or SHA1 works but when asked they can still recommend you a better cryptographic hash. I think everyone should be entitled to opinions and proper response because there is no such thing as a dumb question when it comes to security.
- jfoutz 13y agoThe law is imposed upon you whether you want it or not. With the kernel you're free to take it or leave it. The core of kernel development is free to listen to people, or not. They do seem to want a pretty deep understanding. You're free to just fork the kernel and make it work however you wish. In practice nobody does this. When you're sophisticated enough to explain what you want to the high standards team, it is easier to just make your case to that team.
- nivla 13y ago> The law is imposed upon you whether you want it or not. With the kernel you're free to take it or leave it. Its not always as black and white. There are times when you are forced to use the kernel, maybe a default on your shared hosting that cannot be changed or a restriction put by your team's Administrator for security. Forking is not the effective answer either, its just not practical, its too complex to maintain and upkeep with the new changes. Like you said, in practice nobody does this. Had this not been the case, we would have seen less whining about PHP's problems and more forks to fix it.