Thoughts on Wrapping Libraries

I'm against it. For one simple reason: you can't Google your way out of it.

Custom wrapper methods and properties are often completely undocumented, leaving you with no way to figure out how to use them.

A Real-World Example

At work, we use a table library inside Angular that has been wrapped — and it's a pain to use. Worse, it uses inheritance instead of composition, which makes it even more convoluted and hard to follow.

I Understand the Intent, But...

In large-scale development, wrapping libraries to add shared functionality or enforce consistent design is a common practice — and I get why.

In the old days, when people stayed at a company for years and maintained the same system, having someone who knew the custom wrapper inside-out made sense.

But in today's job-hopping era, if the person who built the wrapper is gone, you're stuck with something you can't Google. Please stop.

Conclusion

That's my case against library wrapping — just sharing something I've been feeling lately.