While I agree with most thing here, I think that in order to make code easier to read, one has to put the semantic upfront. Let me explain. We use language to describe something to another. We don't write code for machine, if we did, we should all be writting asm or even bytecode. We write to other developper. As such the meaning of what we are doing is crucial. I shall quote the "Clean code" bible here: "a good code should be read as a good book". Therefor, I prefer to sort parameters out by meaning rather by lexicography. Anyway, good job. Prettier is indeed a good piece of work. The rust language too has great tool to enforce good code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While I agree with most thing here, I think that in order to make code easier to read, one has to put the semantic upfront. Let me explain. We use language to describe something to another. We don't write code for machine, if we did, we should all be writting asm or even bytecode. We write to other developper. As such the meaning of what we are doing is crucial. I shall quote the "Clean code" bible here: "a good code should be read as a good book". Therefor, I prefer to sort parameters out by meaning rather by lexicography. Anyway, good job. Prettier is indeed a good piece of work. The rust language too has great tool to enforce good code.