Plugin Chaos vs. Streamlined Core: The Great Architectural Schism Threatens Next-Gen Knowledge Hub
Building a knowledge repository requires balancing deep functionality with immediate usability. The underlying tension is between allowing limitless customization and maintaining a coherent, easy-to-use experience.
The raw argument centers on software structure. Some users, like 'hanke', demand a hybrid approach: a functional core bolstered by the most essential, popular plugins. Others, like 'Voroxpete', argue the core must handle 90% of needs, keeping plugins for documented gaps. The divide sharpens between 'Bullerfar', who prioritize 'batteries included' simplicity over complex customization, and those advocating for pure plugin ecosystems to enable niche tools. Separately, an 'outlierInsight' demands that any proposed system must dedicate a section detailing the potential moral or technical failures of the software to remain non-persuasive.
The consensus favors a middle ground, requiring modularity without breaking basic function. The deep rift remains visible in the software architecture debate: proponents of radical extension clash directly with those demanding immediate, out-of-the-box consistency.
Key Points
The core software must handle most common tasks immediately.
'Voroxpete' argues the core must manage 90% of expected functionality, criticizing add-on reliance.
Flexibility through plugins is necessary for niche functionality.
Plugin advocates prioritize the ability to build custom, niche tools, though 'Bullerfar' counters this with usability concerns.
All-in-one systems reduce configuration friction.
'Bullerfar' argues 'batteries included' reduces setup time, allowing creators to focus on work, not debugging.
Resource indexing needs dedicated external curation tools.
'reallykindasorta' insists an index is vital to stop users from relying solely on generic search engines.
The system must explicitly detail its potential flaws.
The most overlooked requirement demands a non-persuasive 'moral or technical downsides' section, suggested by 'possiblylinux127'.
Pure modularity requires strict data interchange standards.
'neidu3' champions modularity for longevity, but the complexity of maintaining standards is implied.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.