Timeline for Differences between the terms Modules, Plugins, Extensions
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2020 at 7:01 | comment | added | Christophe | @C.L. Thank you for this very intuitive summary. Maybe you could add "and that taken alone is useless" to your informal plugin definition. The issue I have with extending is that different people use it for very different purpose. For a java developper extending is very concrete. And for an ERP vendor a "module" may extend functionality of other "thingies" ;-) | |
| Oct 2, 2020 at 6:36 | comment | added | C.L. | Module - group of thingies. Plugin - ready to use thingy that adds functionality. Extensions - thingy that extends functionality of other thingies. | |
| S Apr 20, 2016 at 4:39 | history | suggested | David Refoua | CC BY-SA 3.0 |
corrected some spelling and improved formatting.
|
| Apr 20, 2016 at 1:13 | review | Suggested edits | |||
| S Apr 20, 2016 at 4:39 | |||||
| Apr 20, 2016 at 1:00 | vote | accept | David Refoua | ||
| Apr 19, 2016 at 23:01 | comment | added | Jörg W Mittag | Some other interesting and/or important module systems: Racket's Units, Standard ML's Parameterized Functors, and Newspeak and Scala are interesting, because they unify modules with objects and module definitions with classes (traits). Scala's type system, specifically, has been extended with features that are explicitly intended to match features normally found in module systems. That way, Newspeak and Scala don't need a separate module system, plus first-class and higher-order modules are completely natural: modules are just objects, and objects are obviously first-class in OO. | |
| Apr 19, 2016 at 21:52 | history | answered | Christophe | CC BY-SA 3.0 |