Plugin Oriented Programming A New Way to Scale Development
summary
Claim: making every component a plugin scales maintainability. Implementation: a Python runtime called pop with a hierarchical hub and plugin subsystems, a project generator pop seed, and a builder pop build that wraps PyInstaller to produce single binaries (~20MB today, aiming 7–10MB). Evidence: ~50 active contributors and POP-based services running in production across thousands of datacenters; features demonstrated include unified config loading, app merging for seamless composition, and working deployments of merged applications.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:12Augmented plugin oriented programming
- 2:00Plugin oriented programming adoption
- 2:50History of programming paradigms
- 7:16Problems with objectoriented programming
- 12:27PluginOriented Programming
- 14:27UNIX Philosophy
- 20:14Creating a Plugin Oriented Project
- 22:13Running the Plugin Oriented Project
- 26:48The Hierarchical Model
- 29:32The Configuration Loading Problem
- 34:30Pop Build
- 40:02Additional Projects
related talks
41mHow to Grow an Open Source Project: A Case Study of Python
38mHow to Flatpack Programs
50mPanel Discussion: The Parallel Universes of ISPOs and OSPOs
05mVoxpopuli
30mExtensible Python: Robustness Through Addition
34mIntroducing PIP.Services, a new open-source toolkit for enterprise-level microservice creation
32mReinventing the Wheel: A Community-Driven Roadmap for Python Packaging
50mBuild Software Like a Bag of Marbles, Not a Castle of LEGO
