Rage Against the Ecosystem
summary
Claim: Fury is a source-based dependency manager that defines builds as data not code and replaces binary publishing pain with source-based dependencies. It uses the bloop backend to compile and demonstrates building Fury from source in ~30–60s locally. Workspaces and schemas enforce coherent, publishable sets of projects, you can fork imported repos into editable checkouts, and publishing becomes tagging a signed commit. Source is public, private beta and Windows/enterprise support are in progress.
AI-written summary · about
chapters (22)
- 0:00Introduction to Fury
- 1:19Builds as data not code
- 3:05Source dependencies advantages
- 5:57CLI and interactive builds
- 9:10Modules and compilation
- 11:25Bloop backend integration
- 13:13External library dependencies
- 15:46Forking and contributions
- 17:13Workspaces and projects
- 19:24Workspace inheritance
- 23:24Schemas for cross-building
- 27:36Resolving diamond dependencies
- 31:28No plugins in Fury
- 33:59Plugin-like behavior with modules
- 36:52Common build tool features
- 37:34Maven Central limitations
- 40:52Fury release and support
- 43:48Virtus Lab partnership
- 46:04Future development plans
- 47:51Roadmap and timeline
- 49:02Source code now public
- 50:05Q&A and closing
related talks
55mComponent Driven Repo for a Component Driven World
51mMoving at the Speed of Thought
45mLess is More - a Build Pipeline for the Modern Age
01h 01mWhy managing C++ dependencies is hard
20mBuilding with Monorepos
24mManaging Dependencies with Confidence
26mRethinking Developer Infrastructure
31mBazel: Do We Really Need Another Build Tool?