-
Notifications
You must be signed in to change notification settings - Fork 2k
What do you mean by "GUI simplicity"? #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sort of both at once. The full set of Git's functionality is large and complicated, so most GUIs choose to implement a task-focused subset. This is definitely simpler for the user (while at the same time being a bit limiting), but it's also easier for the developer since they don't have to implement all of Git's features. Does that make sense? |
Do you suggest that I translate the word "simplicity" literally, leaving the thinking to the readers? |
I'm afraid that decision lies with you, since you know the language and how readers will interpret it. 😄 |
I would lean more towards #2 as the meaning of that sentence. Often it's more work to put in fewer features for the sake of making the GUI approachable and simple. I would say that we're saying it's to make the interface simpler, not the implementation of the application. |
Less is more. I like that. |
I'm working with the zh translation and I need a clarification.
About the line in
progit2/book/01-introduction/sections/command-line.asc
.What do you mean by "simplicity"? We've got two possible explanation.
Would you please elaborate on that?
The text was updated successfully, but these errors were encountered: