惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
The Blog of Author Tim Ferriss
Microsoft Azure Blog
Microsoft Azure Blog
S
SegmentFault 最新的问题
Schneier on Security
Schneier on Security
W
WeLiveSecurity
Webroot Blog
Webroot Blog
T
Threatpost
量子位
大猫的无限游戏
大猫的无限游戏
C
Cisco Blogs
腾讯CDC
N
News | PayPal Newsroom
T
Troy Hunt's Blog
T
Tailwind CSS Blog
Latest news
Latest news
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
The Register - Security
The Register - Security
Know Your Adversary
Know Your Adversary
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Engineering at Meta
Engineering at Meta
SecWiki News
SecWiki News
MyScale Blog
MyScale Blog
GbyAI
GbyAI
Application and Cybersecurity Blog
Application and Cybersecurity Blog
A
Arctic Wolf
The GitHub Blog
The GitHub Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Help Net Security
Help Net Security
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
有赞技术团队
有赞技术团队
NISL@THU
NISL@THU
L
LINUX DO - 最新话题
雷峰网
雷峰网
P
Privacy International News Feed
Spread Privacy
Spread Privacy
Attack and Defense Labs
Attack and Defense Labs
N
News and Events Feed by Topic
月光博客
月光博客
V
V2EX
H
Help Net Security
博客园 - 三生石上(FineUI控件)
U
Unit 42
B
Blog
PCI Perspectives
PCI Perspectives
G
GRAHAM CLULEY
Stack Overflow Blog
Stack Overflow Blog
P
Proofpoint News Feed
T
Threat Research - Cisco Blogs
Last Week in AI
Last Week in AI

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Epic Games Open-Sourced Lore — A Version Control System Built for Massive Game Assets
Md Jamilur Rahman · 2026-06-18 · via DEV Community

Epic Games just dropped something that could reshape how game studios handle code and assets. They've open-sourced Lore — a centralized version control system built from the ground up to solve one painful problem: managing enormous binary files alongside source code.

This isn't another Git wrapper. It's a completely new VCS, written in Rust, MIT-licensed, and battle-tested behind Fortnite's UEFN (Unreal Editor for Fortnite) toolkit.

Why Does the World Need Another VCS?

Git is brilliant for text-based code. But game development isn't just text. It's 4K textures, uncompressed audio, rigged 3D models, animation sequences, and massive world maps. These files can be hundreds of megabytes each.

Git wasn't designed for this. Git LFS (Large File Storage) helps, but it's a patch on top of a fundamentally text-oriented system. Perforce Helix Core has been the industry standard for game studios for decades — but it's proprietary, expensive, and closed-source.

Epic Games looked at this landscape and said: we can do better.

What Is Lore?

Lore is a centralized, content-addressed version control system optimized for:

  • Large binary assets — textures, meshes, audio, video
  • Massive teams — hundreds of developers working simultaneously
  • Hybrid projects — code + binaries in the same repository
  • Sparse checkouts — developers only download what they need

Think of it as Perforce's philosophy (centralized, binary-friendly) combined with Git's content-addressed storage model, wrapped in Rust's performance guarantees.

How It Works Under the Hood

Lore's architecture is built around a few key technical decisions:

Content-Addressed Storage

Every piece of data is stored and referenced by its content hash. This means:

  • Automatic deduplication — identical content is stored once
  • Integrity verification — any tampering changes the hash
  • Efficient caching — content can be cached anywhere in the pipeline

Merkle Trees & Immutable Revision Chain

Revision hashes are cryptographically derived from parent hashes and data hashes. This creates a tamper-evident chain of history — similar to how Git works internally, but applied to binary-heavy workflows.

Chunked Storage

Large files aren't stored as monolithic blobs. They're split into reusable chunks. When a 200MB texture changes 5% of its data, Lore only stores the changed chunks — not the entire file again.

On-Demand Hydration

Developers don't download the entire repository. Workspaces fetch file data only when needed. Working on the UI? You don't need the 50GB of audio files sitting on your disk.

Centralized with Caching

Lore uses a centralized server (like Perforce), but adds intelligent caching to scale throughput. This gives teams a single source of truth while avoiding the bottleneck of every request hitting the origin server.

Key Features

Fast and Efficient
Shared, reusable data chunks and on-demand downloads keep operations fast even with terabyte-scale repositories.

Free Branching
Lightweight, low-overhead branching for experimentation and release management. No more "I'm scared to branch because it'll take 20 minutes."

Trustworthy History
Verifiable, tamper-evident source of truth. Every revision is cryptographically signed.

Full CLI Interface
Complete functionality via command line. No GUI dependency — integrate with whatever workflow you want.

Multi-Language API
Extend Lore via bindings for C/C++, C#, Rust, Go, Python, or JavaScript. Build custom tooling, integrate with your pipeline, automate anything.

The SDK Ecosystem

Lore isn't just a CLI tool. It's a platform:

SDK Language Use Case
Core Rust Server, library, CLI
lore-js JavaScript Web tooling, CI/CD
lore-python Python Pipeline automation
lore-dotnet C# Unity/Unreal integration
lore-go Go Backend services

Getting Started

Lore ships with a demo mode for immediate experimentation:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash -s -- --demo

# Windows (PowerShell)
$env:LORE_DEMO = 1; irm https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.ps1 | iex

The latest release is v0.8.3 — still pre-1.0, but functional and under active development.

Lore vs Git vs Perforce

Feature Git Git LFS Perforce Lore
Large binary support Poor Better Excellent Excellent
Open source
Cost Free Free $$$ Free
Content-addressed Partial
Chunked dedup
Sparse checkout Partial Partial
On-demand hydration
Built for binary assets Somewhat
Merkle tree integrity

Who Should Care?

Game studios — obvious. If you're shipping AAA titles with massive asset pipelines, Lore is built for you.

Film & VFX — same problem. Huge binary assets, multiple contributors, tight deadlines. Lore's architecture fits.

Enterprise software — any project with large binaries (ML models, datasets, media files) could benefit.

Open-source enthusiasts — Epic just gave the world a free, MIT-licensed alternative to Perforce. That's significant.

Current Limitations

Lore is pre-1.0. The team explicitly warns that interfaces, on-disk formats, and APIs may change between releases. The UEFN build currently uses a proprietary compression format not available in the open-source version.

It's also centralized by design — no distributed model like Git. For some teams, that's a feature. For others, it's a constraint.

Why This Matters

Epic Games didn't open-source Lore out of charity. They built it because Git and Perforce weren't good enough for Fortnite's development pipeline — a game with terabytes of assets, hundreds of concurrent developers, and daily updates.

By open-sourcing it, they're:

  1. Attracting contributors to improve the tool they depend on
  2. Building ecosystem lock-in — if studios adopt Lore, they're more likely to stay in the Unreal ecosystem
  3. Undercutting Perforce — free alternative to an expensive competitor

It's a smart business move disguised as community goodwill.

What's Next?

The Lore team is actively developing toward 1.0. The roadmap likely includes:

  • Stabilizing APIs and on-disk formats
  • Expanding the SDK ecosystem
  • Building GUI tooling
  • Enterprise features (SSO, audit logs, permissions)

The GitHub repo already has 808 stars and a growing community on Discord. If you're in game dev or working with large binary assets, Lore is worth watching.


Links:


Based on EpicGames/lore on GitHub and Epic Games announcement