Key Concepts: Git interface, CVS (Concurrent Versions System), subcommand naming, user expectations, design choices.
The speaker discusses the initial negative feedback received regarding the Git interface, specifically focusing on the naming conventions of Git subcommands. The core issue stemmed from user expectations based on their experience with CVS.
User Complaints and Naming Conventions:
The speaker highlights the volume of complaints received about the Git interface, particularly the naming of subcommands. Users questioned why Git's subcommands differed from CVS, perceiving these differences as arbitrary and without justification. The speaker admits to intentionally deviating from CVS naming conventions.
Motivation for Divergence from CVS:
The primary reason for the different naming scheme was the speaker's dissatisfaction with CVS. This dislike motivated a deliberate effort to implement things differently in Git, even if it meant diverging from established conventions.
git status Example:
The speaker mentions git status as an example. While git status is now a frequently used command, the speaker notes that they rarely used an equivalent command in CVS due to its slowness. This illustrates how performance considerations and personal preferences influenced the design of Git.
Early Years and Flame Wars:
The speaker recalls the first few years of Git's existence as a period marked by intense debates ("flame wars") over the choice of names for subcommands. This underscores the strong opinions and expectations users had regarding version control systems.
Conclusion:
The speaker's decision to deviate from CVS naming conventions in Git was a conscious choice driven by dissatisfaction with CVS and a desire to improve upon its shortcomings. This decision, however, resulted in significant user pushback and debates, particularly in the early years of Git's adoption. The example of git status highlights how performance and personal preference played a role in shaping Git's design, even if it meant breaking with established norms.
AI summaries can miss context or contain errors. Check important details against the original video.
