From d3f72a02f036ab22636be786833a22a7e89d1c65 Mon Sep 17 00:00:00 2001 From: Chris Hodapp Date: Sat, 22 Apr 2017 11:42:36 -0400 Subject: [PATCH] Scraps for 'modularity' post I planned --- posts/2017-04-20-modularity.md | 40 ++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 posts/2017-04-20-modularity.md diff --git a/posts/2017-04-20-modularity.md b/posts/2017-04-20-modularity.md new file mode 100644 index 0000000..4032eb9 --- /dev/null +++ b/posts/2017-04-20-modularity.md @@ -0,0 +1,40 @@ +--- +title: Modularity (working title) +author: Chris Hodapp +date: April 20, 2017 +tags: technobabble +--- + +- Nix, Guix +- [[Notes - Distributed stuff notes (from turtl)]] +- [[Notes - Paper, 2016-11-13]] +- See notes on functional geekery #75 +- Jupyter +- Any Plan 9 papers? (Will have to dig deep in the archives) + - http://plan9.bell-labs.com/sys/doc/ +- Tanenbaum vs. Linus war & microkernels +- Abstraction vs. modularity + - tbl_design quote: "Modular design hinges on the simplicity and abstract nature of the interface definition between the modules. A design in which the insides of each module need to know all about each other is not a modular design but an arbitrary partitioning of the bits." +- Modules: Most useful when available in the most general or most accessible context, versus more specific, more restricted contexts? (e.g. Linux commandline tool vs. a Wordpress plugin or an Emacs package) - the TBL quote on least-power sort of corroborates this. +- hypothes.is is a sort of module unto itself here too, trying to remove commenting and annotation from existing, very siloed solutions. +- "Self" paper & structural reification? +- What by Rich Hickey? +- SICP? +- "On Understanding Data Abstraction, Revisited" +- Frameworks Don't Compose ([composition][]) + +- Abstraction enables modularity. Why: Abstraction barriers are what separate modules. +- The modules that make sense may change over time. ("Have modern tools tried to keep embodying the 'Unix philosophy'? Have they extended it, even to other forms of abstraction that weren't previously considered?") + +[taoup]: http://www.catb.org/~esr/writings/taoup/html/ "The Art of Unix Programming (Eric S. Raymond)" +[future]: https://circleci.com/blog/its-the-future/ "It's the Future" +[future2]: https://circleci.com/blog/it-really-is-the-future/ "It really is the future" +[attvideo]: https://www.youtube.com/watch?v%3Dtc4ROCJYbm0 "AT&T Archives: The UNIX Operating System" +[ezyang_pkg]: http://blog.ezyang.com/2014/08/the-fundamental-problem-of-programming-language-package-management/ "The fundamental problem of programming language package management" +[npmgate]: https://www.reddit.com/r/programming/comments/4bjss2/an_11_line_npm_package_called_leftpad_with_only/ +[geekery75]: https://www.functionalgeekery.com/episode-75-eric-b-merritt/ +[w3]: https://www.w3.org/DesignIssues/ +[tbl_modularity]: https://www.w3.org/DesignIssues/Modularity.html +[tbl_design]: http://www.w3.org/DesignIssues/Principles.html +[sword]: http://www.freecode.com/articles/editorial-the-two-edged-sword +[composition]: https://clojurefun.wordpress.com/2012/08/17/composition-over-convention/