I can somewhat see why people would change argument order, when importing a function, as a means to maintain consistency and expectations within the project importing it – similar to how you wouldn’t just import code with wildly different formatting into a project, you would format it according to the conventions of the project.
I also see the point the post is making that having methods named the same thing across various BSD, but with different signatures would be confusing at best. Also not good.
As far as why some of the methods are being imported, keeping signatures, and then making them wrappers to things have wildly different behavior, I am having a harder time understanding. That seems a far less defensible position.
aside: I had a good chuckle at “Avant-garde web site design”. tedu should have made this particular post use comic sans, so everyone could have ignored it and focused instead of discussing the font choice. ;)
I can somewhat see why people would change argument order, when importing a function, as a means to maintain consistency and expectations within the project importing it – similar to how you wouldn’t just import code with wildly different formatting into a project, you would format it according to the conventions of the project.
I also see the point the post is making that having methods named the same thing across various BSD, but with different signatures would be confusing at best. Also not good.
As far as why some of the methods are being imported, keeping signatures, and then making them wrappers to things have wildly different behavior, I am having a harder time understanding. That seems a far less defensible position.
aside: I had a good chuckle at “Avant-garde web site design”. tedu should have made this particular post use comic sans, so everyone could have ignored it and focused instead of discussing the font choice. ;)