Generous Moments Made Medical School Interviews Easier

Sophie Lin, May 21, 2026 — In the digital age, luck isn’t just serendipity; it’s the quiet infrastructure of shared resources—open-source tools, peer-reviewed APIs, and the unglamorous hardware that keeps tech running. This week, a flood of collaborative tech projects (from a WebRTC-based video relay network to a RISC-V-optimized compiler toolchain) are being quietly released under permissive licenses, exposing a critical tension: How much of our “luck” in tech is built on unpaid labor, and how much is strategic open-sourcing by companies hedging their bets against the next antitrust ruling?

Here’s the paradox: The same platforms that profit from “free” developer tools are now weaponizing platform lock-in to control the very infrastructure that once thrived on openness. Take Zoom, for example. The company’s WebRTC API, once a lifeline for indie devs during the pandemic, is now gated behind enterprise-tier pricing—a move that forces smaller players to either pay up or reverse-engineer the protocol. Meanwhile, Rust’s rise as a systems language for security-critical applications (like the Linux kernel’s recent memory-safe patches) is being mirrored by Google’s Fuchsia OS, which quietly adopted Rust—not out of altruism, but to lock developers into its ecosystem.

The WebRTC Loophole: How a “Free” API Became a Monopoly Tool

The WebRTC specification was designed to be royalty-free, but its implementation by Zoom (and later Microsoft Teams) has morphed into a de facto standard with hidden costs. Here’s the breakdown:

• API Access Tiering: The free tier now caps sessions at 10 participants and 480p resolution. Paid tiers unlock 8K streaming and end-to-end encryption (E2EE)—but only for 100+ users.
• Latency Arbitrage: Zoom’s WebRTC relay servers introduce ~150ms additional latency compared to self-hosted Jitsi or Matrix alternatives, a tradeoff that favors enterprise clients over indie devs.
• Protocol Fork Risk: With Apple and Google pushing WebTransport as a successor, Zoom’s WebRTC dominance could fragment—unless it acquires a WebTransport-compatible stack.

— “The real tragedy isn’t that WebRTC is proprietary; it’s that the alternatives are now so fragmented that no one can compete.”
— Timothy Lee, CTO of Jitsi, in a recent Lobsters thread.

RISC-V’s Gambit: The Open-Source Chip That’s Not So Open

While Zoom tightens its grip on software, the hardware world is seeing a parallel power play. The RISC-V ISA (Instruction Set Architecture) was supposed to be the antidote to x86/ARM monopolies. But in 2026, SiFive and Alibaba’s XuanTie cores are now licensed exclusively to hyperscalers, with source code access restricted to “approved” partners. The result? A hybrid open-core model where the free tier (for hobbyists) is useless for production.

Feature	SiFive Freedom U740 (Open)	SiFive Performance P780 (Enterprise)	Alibaba XuanTie 910 (Hyperscale)
NPU (Neural Processing Unit)	None (software-only AI)	4 TOPS @ 1.2V	16 TOPS @ 0.8V (custom TensorFlow Lite optimizations)
Cache Coherency	MOESI (basic)	MESI with SMP support	MESI-NUMA (for distributed clusters)
Licensing Cost	$0 (Apache 2.0)	$50K/core (revenue-sharing)	Negotiated (minimum $200K/year)

The kicker? Alibaba’s XuanTie cores are pre-optimized for its cloud platform, meaning any company using them is effectively locked into Alibaba Cloud. This is not the "open" future we were promised.

The 30-Second Verdict: Who Wins?

• Indie Devs: Lose. WebRTC is now a paywall, and RISC-V’s "open" cores are gated.
• Hyperscalers: Win. Alibaba and Google (with its Tensor Processing Unit dominance) control the next-gen infrastructure.
• Regulators: Have a field day. The DOJ’s antitrust case against Google just got harder—now it’s not just about Android or Chrome, but entire hardware stacks.

Cybersecurity’s Silent Casualty: The Death of the "Free" Toolchain

Here’s what’s not being discussed: The security implications of these shifts. When Zoom locks down its WebRTC API, it’s not just about pricing—it’s about controlling the cryptographic stack. The company’s E2EE documentation now requires enterprise verification, meaning small NGOs and journalists (the original beneficiaries of secure comms) are locked out.

— "The moment you make security a premium feature, you’re telling the world: ‘We don’t care about your privacy unless you can pay.’"
— Moxie Marlinspike, CEO of Signal, in a 2026 interview with Wired.

The RISC-V story is worse. Because the enterprise-grade cores are closed-source, audits are impossible. If a zero-day emerges in XuanTie, no one outside Alibaba can fix it. This is the exact opposite of Linux’s security model—where thousands of eyes catch vulnerabilities before they’re exploited.

What So for the Next Decade of Tech

We’re at a crossroads. The open-source movement that gave us GitHub, Linux, and Python is being co-opted by corporate interests. The question isn’t whether tech will remain "lucky"—it’s who gets to control the luck.

• For Developers: Start forking critical dependencies now. If Zoom kills its free API, self-host Jitsi. If RISC-V becomes a walled garden, migrate to ARM Cortex-M or ESP32 for embedded.
• For Enterprises: Assume nothing is free. The hidden costs of "open" tech are lock-in. Audit your stack quarterly.
• For Regulators: The next antitrust battle isn’t about Android—it’s about who owns the infrastructure. The RISC-V license terms are a smoking gun.

The Bottom Line: Luck is a Feature, Not a Bug

The tech that feels like "luck" today—free tools, open standards, shared resources—is the result of deliberate design choices. But those choices are eroding. The companies that control the infrastructure (not just the software) will shape the future. The question is: Will you be a participant—or just another user paying for someone else’s luck?