Open Packages are Overpowered
summary
Claims concrete: NuGet Chocolatey and PowerShell Gallery packages can turn any package into a web server by mapping parts to URIs, and packages act as stackable, memory‑mapped compressed filesystems. Demo shows an unmodified module served with README and SVGs, 47 functions enumerated, live edits reflecting instantly, and REST verbs allowing GET PUT POST DELETE against parts. Enumeration runs about 20x faster than disk, streams allow in-place edits, and the OP module is published at github.com/poshwebop.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:24Open packages overview
- 5:12Open packages as web servers
- 9:04Using open packages in PowerShell
- 14:24OP PowerShell module
- 15:31Live demo: OP module
- 24:47PowerShell module to web app
- 28:22Real-time package edits
- 30:10Open packages use cases
- 33:03Performance benefits
- 34:58AI workflows efficiency
- 35:42Inspecting PowerPoint as package
- 37:31Anything as package
- 38:55Why open packages broken
- 41:51PowerShell for web dev
- 43:14Q&A
related talks
13mWeird NuGet Packages: A Playground for Creativity in .NET
31mIt's a Jungle Out There: What's Really Going on Inside Your Node_Modules Folder, Feross Aboukhadijeh
32mIt's a Jungle Out There! – Open Source Supply Chain Attacks
43mHow to hack and defend (your) open source
25mTrusting Your Open-Source Software Supplier
21m#7 Open Source Forum 2019 Dan Lorenc
32mUncharted packages
18mBuilding pi in a World of Slop