2 ms·
Can't help but link to IMO the best piece on libraries vs frameworks: "I’d really like to give you this fork Jimmy, but you’re gonna need a knife and plate to u
by cousin_it 18y ago
Can't help but link to IMO the best piece on libraries vs frameworks: "I’d really like to give you this fork Jimmy, but you’re gonna need a knife and plate to use it." http://an9.org/devdev/why_frameworks_suck http://an9.org/devdev/why_frameworks_suck
- SwellJoe 18y agoSounds like CPAN would be more his style, rather than hanging around in the library ghetto with Python. (I should probably be running now, before the snake handlers arrive, huh?)
- Hexstream 18y agoThat seems a gripe about monolithic frameworks... There's no reason a framework can't be organised as a coherent collection of libraries of which you can pick only the ones you need and that lets you assemble an "instantiation" of the framework by choosing a variant of each type module you need.
- cousin_it 18y agoHere'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".