Having read the first two parts of Reactivity Tips and Tricks I think you may like the TidyModule approach to modules more than stock. They use R6 class objects to hold both the UI and Server functions of a module as well and created a built in port system for piping data in and out of their modules.
If you're making apps with lots of repeated complicated code blocks it's imho a much better approach than stock modules, although if a majority of your app consists of individual bespoke pieces I'd just as soon skip the OO approach entirely. Sometimes all you want is a banana and not a gorilla troop factory to produce a stateful gorilla to hold the banana. Since we spend easily several times as much time reading code as writing it I'm a fan of balancing clever parsimony against clear legibility.
Having read the first two parts of Reactivity Tips and Tricks I think you may like the TidyModule approach to modules more than stock. They use R6 class objects to hold both the UI and Server functions of a module as well and created a built in port system for piping data in and out of their modules.
If you're making apps with lots of repeated complicated code blocks it's imho a much better approach than stock modules, although if a majority of your app consists of individual bespoke pieces I'd just as soon skip the OO approach entirely. Sometimes all you want is a banana and not a gorilla troop factory to produce a stateful gorilla to hold the banana. Since we spend easily several times as much time reading code as writing it I'm a fan of balancing clever parsimony against clear legibility.