<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on NV Trends</title><link>https://blogs.nvtrends.com/tags/git/</link><description>Recent content in Git on NV Trends</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 02:26:43 +0000</lastBuildDate><atom:link href="https://blogs.nvtrends.com/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Lore: The Open Source VCS Revolutionizing Scalability</title><link>https://blogs.nvtrends.com/posts/2026/lore-open-source-version-control-scalability/</link><pubDate>Thu, 18 Jun 2026 02:26:43 +0000</pubDate><guid>https://blogs.nvtrends.com/posts/2026/lore-open-source-version-control-scalability/</guid><description>&lt;p&gt;For nearly two decades, Git has been the undisputed king of version control. Whether you are a solo developer working on a hobby project in Bengaluru or a software engineer at a global tech giant, Git is likely the tool you use to manage your code. It revolutionized the way we think about branching, merging, and collaboration. However, as software projects have grown in complexity—merging massive codebases with gigabytes of binary assets—the cracks in Git’s foundation have started to show. Developers working on massive game engines, machine learning models, or enterprise-scale monorepos often find themselves fighting against the very tool meant to help them.&lt;/p&gt;</description></item></channel></rss>