| > "all 3rd-party libraries are a potential liability." Yup. Even if they are responsive today, doesn't mean they will be, tomorrow. My views on The Dependapocalypse are not usually welcome, in modern discussions of software strategy. Not exactly sure why they are using string(describing:) in ship code. I suspect the architecture may need a bit of a look-see. I only use it in debug tracking. It's the reflection API, and that's not really something I'd consider for runtime. Sort of like using exceptions for branching. It works, but your results may not be optimal. UPDATED TO ADD: I did think of one place I might use it (actually, the ".description" computed property), and that's in a "one-off" bit of code that may be doing something like figuring out how to deal with some JSON I parsed, or reading stored prefs. Otherwise, I've usually figured out other ways to deal with it. One advantage I have, is I seldom use third-party libraries, and can actually go into my modules, and tweak them to serve the frontend better (in fact, I just did exactly that, this morning). |