[BigJono]

> Yeah, and in CR you should be told not to use the object form when you have "true" as the value, as it's pointless. That's what string form is for. The "docs" are literally 5 lines where you learn you can send object literals, arrays and strings.

What a dumbass argument. So instead of writing a one line abstraction, I should invest a bunch of CR time explaining to my whole team which of 3 different APIs they should be using in this dependency I've brought in?

> Holy cow, man. Do you literally hand-implement EVERY utility function you've ever needed?

No, just the trivial ones. Have you been actually reading this thread?

> Your point seems to be: you can't manage to infer ANYTHING from a function signature

No, my point is that you can't infer the full API of a function from the arguments passed to it's invokation when the function is polymorphic.

> AND that apparently somehow your team members can ALWAYS infer everything needed from any function YOU write.

If the function is trivial, which is exactly what we've been talking about this whole time, then No. Fucking. Shit. The function is trivial and they have the source code right there.

[jhall1468]

> So instead of writing a one line abstraction, I should invest a bunch of CR time explaining to my whole team which of 3 different APIs they should be using in this dependency I've brought in?

It's not a one-liner because it doesn't support the same feature set. It supports a basic use case that may be great for trivial apps, but in the real world it isn't.

> No, just the trivial ones. Have you been actually reading this thread?

And said trivial ones must still be "learned" by your co-workers. You've saved exactly zero time.

> No, my point is that you can't infer the full API of a function from the arguments passed to it's invokation when the function is polymorphic.

You can with a glorified text-editor these days with Code Inspection. I guess that's advanced stuff we shouldn't expect our co-workers to use?

> If the function is trivial, which is exactly what we've been talking about this whole time, then No. Fucking. Shit. The function is trivial and they have the source code right there.

Yet, if the function is trivial AND is imported via npm, it suddenly requires reading docs. On one hand you argue "triviality requires reading docs" and then suggest that you can implement a similar trivial function and everyone can just look at the source code.

And you don't see the irony here.

[BigJono]

You're conflating a trivial function with a trivial API. The whole reason I jumped into this thread is because classnames is a great example of a trivial function with a non-trivial API. Yes, you do need to look up either the docs or the implementation to understand how to use it. I think my past examples made that clear.

What I'm saying is that it's EASIER to understand the source code than it is to understand the documentation for classnames. That's because it abstracts nothing away. It's replacing one simple API (template strings) with another one that's very similar and of roughly the same power. By turning it into a dependency you're adding an artificial barrier between it and your code base, that makes it harder for everyone to grok. Not much harder, but enough to be a pain in the ass in any codebase where that same tradeoff is made over and over.

If you can't understand that, then I don't know what to do for you. Keep writing shit JS code and making the web worse than it already is.