2 ms·
That's fine. But the cultural acceptance of single-function libraries is still a problem. Before NPM, it wasn't even an issue - plenty of javascript libraries a
by krapp 8y ago
That's fine. But the cultural acceptance of single-function libraries is still a problem. Before NPM, it wasn't even an issue - plenty of javascript libraries and jQuery plugins were being distributed that way.
Why does a function to check if a number is even need its own namespace, and a dependency on another namespace which tests if it's a number at all, and a third to check if it's odd? What's the benefit to this?
>I suppose it's similar to the Unix philosophy, "do one thing and do it well"
Any philosophy can be taken too far.
- gitgud 8y ago> Why does a function to check if a number is even need its own namespace, and a dependency on another namespace which tests if it's a number at all, and a third to check if it's odd? What's the benefit to this? The benefit is modularity, separation of concerns and versioning but in this case it's ridiculous... Any philosophy can be taken too far That should be printed on my office wall!