Notice of Obsolescence
ggaughan
20 points
1 comment
April 28, 2026
Related Discussions
Found 5 related stories in 82.2ms across 8,303 title embeddings via pgvector HNSW
- We Added a Console Notice to Internationalizationext – and Why We Removed It screeny05 · 12 pts · March 29, 2026 · 44% similar
- The 90 Day disclosure policy is dead unknownhad · 16 pts · May 09, 2026 · 42% similar
- Warranty Void If Regenerated Stwerner · 261 pts · March 18, 2026 · 41% similar
- Warranty Void If Regenerated Stwerner · 92 pts · March 17, 2026 · 41% similar
- Google Just Patented the End of Your Website bookofjoe · 39 pts · March 27, 2026 · 41% similar
Discussion Highlights (1 comments)
kindkang2024
> The companies that benefit most from it contribute disproportionately less than their benefit. We covered the structural reason for this in the previous post on PostgreSQL’s licensing — permissive licenses are an invitation to use freely, and the invitation is widely accepted. pgBackRest is the same problem in personal form. Not a license issue; a payroll issue. On the licensing point, here's my wildest imagination: what if those permissive licenses had one small condition — companies profiting from the project must contribute a tiny fraction toward social good? No profit, no obligation. I think this actually matches what most maintainers originally wanted. They go open-source for influence and respect, trying to make the world better, making their work freely usable by anyone, even competitors. Given that, it's quite reasonable to ask those who profit from it to share a tiny fraction back with the world. Open source projects may die, but the love and spirit behind them doesn't — and a profit-sharing clause like this could make that spirit more explicit and more undeniable.