> For example if an object already does have an idiomatic API, it’s probably not worth wrapping in an identical façade, just so it belongs to you. Ooooh my gwa

> For example if an object already does have an idiomatic API, it’s probably not worth wrapping in an identical façade, just so it belongs to you. Ooooh my gwahh... your third party library better surely has an idiomatic API - otherwise search a better one or please don't expect your average developer come up with one. I have seen this too often, countless attempts of unecessary wrappers added around fine APIs because we need to own it more, test it better or replace it in some very eventual future.. and what you get is almost always less idiomatic APIs, that transform results badly like swallowing errors, and what else, often requiring me to now learn two APIs, a badly documented but owned one (or just read the source code!!!) and the real one. Sure I hear what the author says.. but practice with the average dev and this turns out different in reality :(