TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: What are your version control pain points?

1 点作者 yashp将近 4 年前
Whether it&#x27;s git or hg or p4... what do you wish your VCS could do differently? Do you feel constrained by size or scale? Do you wish it were less sluggish? More flexible or easy to use? Easier to customize for your team&#x27;s processes or workflows?<p>To give one example, I&#x27;ve worked at multiple companies where the codebase was split across many git repos, and the slew of repos made everything harder to coordinate, develop, and understand. Maybe this resonates with you -- or maybe you have other problems?<p>(Context: I build developer tools, including currently a VCS. Nothing is more compelling to me than the day-to-day struggles of a developer who just wants to ship their code, god damn it.)

1 comment

elviejo将近 4 年前
I want a VCS that treats code as an AST not as text because: That way meaningless white-space changes, wouldn&#x27;t cause a diff. Renaming a function would be just that a rename, not a 100 lines with + and -. Where every commit is recorded (ala Fossil)... but where a set of commits can be seen as if was just one. (So that a meaningful set can be seen as what it was).