Labs/Jetpack/Reboot/Best Practices: Difference between revisions

added another bullet point
(Added question about how Cuddlefish modules are used)
(added another bullet point)
Line 14: Line 14:
* API design
* API design
* Some Cuddlefish modules, like file.js, take pains to be broadly compatible as JS modules and loadable as-is in Web pages, in addition to being SecurableModules used in Jetpack.  Do we really want to go that route for all modules?
* Some Cuddlefish modules, like file.js, take pains to be broadly compatible as JS modules and loadable as-is in Web pages, in addition to being SecurableModules used in Jetpack.  Do we really want to go that route for all modules?
* Creating code that can exist side-by-side with different versions of itself; implies not mutating the outside environment in certain ways.
874

edits