Here's my humble perspective on code reachability and the fork/knife/plate thing. Good: a library function with no dependencies, that accepts and returns primi

Here's my humble perspective on code reachability and the fork/knife/plate thing. Good: a library function with no dependencies, that accepts and returns primitive data structures. Worse: a library with lots of dependencies, and a set of idiotic "data types" or "classes" I have to construct just to access the functionality. Worst: a "framework" that calls your code itself, and requires a specific "environment" that should be "set up properly".