git ultimately falls to the same issue as to why not everyone is a Linux user. Both systems are built on the idea that there should be lots of small tools that handle 1 thing.
The issue with this sort of design system is lack of abstraction. Us developers can easily be the type that "wants the control", so systems built with lots of smaller tools that together handle large amounts of use-cases with minimal or no abstraction seems appealing in theory.
However, in practice it means needing to understand a lot of tools/features just to perform simple tasks that should or could be straight forward with an abstraction.
Ultimately there comes a time where there is a "better tool" that abstracts away most of the underlying complexity. However, git does its job really well, and the alternatives have too many pitfalls to be considered seriously. Because of that, git has become the choice, for better or worse.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
The design principle from Alan Key is that Simple things should be simple, complex things should be possible.
There is a mentality common to Linux and git (started by the same guy...) that you start by the second half and the first half with somehow sort itself out.
Nope.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
gitultimately falls to the same issue as to why not everyone is a Linux user. Both systems are built on the idea that there should be lots of small tools that handle 1 thing.The issue with this sort of design system is lack of abstraction. Us developers can easily be the type that "wants the control", so systems built with lots of smaller tools that together handle large amounts of use-cases with minimal or no abstraction seems appealing in theory.
However, in practice it means needing to understand a lot of tools/features just to perform simple tasks that should or could be straight forward with an abstraction.
Ultimately there comes a time where there is a "better tool" that abstracts away most of the underlying complexity. However,
gitdoes its job really well, and the alternatives have too many pitfalls to be considered seriously. Because of that,githas become the choice, for better or worse.The design principle from Alan Key is that Simple things should be simple, complex things should be possible.
There is a mentality common to Linux and git (started by the same guy...) that you start by the second half and the first half with somehow sort itself out.
Nope.