proomt

Search

Search posts, papers, and topics

All posts

Hacker News front page23 min readintermediate

Nobody pays for FOSS, we can force them to

Summary

The post argues that the free‑software model (MIT/BSD/Apache licenses) is an evolutionarily stable strategy: anyone can use the code for free, and attempts to charge via restrictive licenses fail because forks quickly replace them. This stability comes at a human cost—most maintainers are unpaid, many burn out, and the rapid velocity of modern ecosystems (npm, cloud services) amplifies the mainte…

  • Open‑source projects that try to monetize via license restrictions are routinely forked and lose market share; the free‑software license regime remains dominant.
  • Maintainer economics are dire: ~60 % of open‑source maintainers are unpaid, a tiny minority receive any funding, and a handful of developers own the majority of critical code.
  • The acceleration of software adoption (npm, cloud services) has increased the maintenance cost per project without raising compensation, turning maintainership into an unpaid second job.
  • Existing interventions—tips, foundation salaries, corporate pledges, security‑focused funding—are too small relative to the trillions of dollars the ecosystem generates and fail to alter the underlying equilibrium.

Enterprise reliance on open‑source creates a hidden, unsustainable labor model. When critical packages are maintained by overworked volunteers, security and reliability risks rise, as illustrated by the xz backdoor incident. Understanding the economic forces helps teams evaluate risk, contribute re…

5/10

Related reading

  1. CloudBees vs Harness: Why Migration Isn't the Fix

    The article argues that Harness’s “free migration” offer hides significant downstream costs (training, pipeline rebuilds, compliance recertification) and that even after migration you still lack unified governance across heterogeneous CI/CD tools. CloudBees positions its Unify control plane as a tool‑agnostic layer that adds visibility, continuous governance, AI‑driven test selection, and hybrid…

    Codeshipcloudbees.com5 min
  2. I expected better from Google

    The authors of the open‑source project mobile‑use discovered that Google’s Artemis repository contains large blocks of identical Python code, examples, and even the same agent name without any attribution. They document the exact file diffs, the removal of their names via a force‑push, and the omission of their benchmark results from a public leaderboard. The post argues that this violates Apache…

    Lobstersminitap.ai6 minHN18032lobste.rs87
  3. Why I'm still bearish on LLMs after Navier-Stokes

    The author argues that despite headline successes (e.g., Navier‑Stokes proof, security exploits), current frontier LLMs still require heavy human oversight and rigorous specifications that are costly to produce. Reward‑hacking, narrow generalization, and the need for domain‑expert spec writing limit autonomous deployment to only a few niche domains (high‑failure‑cost work, tightly defined tasks,…

    Hacker News front pagedank.systems5 minHN487644lobste.rs49
  4. Who Owns AI-Generated Code Failures?

    AI‑generated code breaks the traditional chain of ownership: developers merge PRs they didn’t write, reviewers approve logic they didn’t originate, and QA validates tests chosen by a model. A CloudBees survey shows 81% of firms see more production failures from AI code, and accountability often drifts upward to CTO/VP. The post argues role‑based accountability isn’t enough; you need end‑to‑end tr…

    Codeshipcloudbees.com4 min
  5. Changing the game: How Google uses agentic AI to secure hundreds of millions of lines of code

    Google’s AI & Infrastructure team built an agentic pipeline (Mantis) that runs pre‑submit AI‑driven scans on every code check‑in, validates findings with a fast triage agent (AST + call‑graph analysis) achieving >92% precision in <1 min, then auto‑generates fixes via a bug‑fix agent. Localized threat models and a two‑step scan cut false‑positives to ~3% and prevent hundreds of vulnerabilities eac…

    Google Cloud Bloggoogle.com4 min
  6. AWS reimagines the getting started experience

    AWS announced a new “project” onboarding flow that lets new users start building with default configurations, free credits, and simplified IAM handling. Sign‑in via Google/GitHub/Apple creates an isolated AWS account, auto‑provisions a CLI/agent toolkit, and lets you invite collaborators by email. Spend limits can be set per project, and advanced features (multi‑region, org policies) can be enabl…

    AWSamazon.com5 minHN33