4 ms·
I think worse is better here. This just sounds like another layer of abstraction and complexity i want to avoid dealing with as it will consume head space and d
by bgar 14y ago
I think worse is better here. This just sounds like another layer of abstraction and complexity i want to avoid dealing with as it will consume head space and detract from actually solving the problem i am there to solve.
I have a similar opinion, although I don't usually stick to defaults.
Apparently this is targeted to teams of developers, so there might be more of a need to "modularize" things.
- hp50g 14y agoHaving dealt with teams of developers and existing within them, I doubt this would impact them in any positive way. It would in some animal-farm-esque way empower an individual rather than everyone. People have so many differing opinions on such things, standardisation is hard.
- twe4ked 14y agoThe idea with modularizing things is it makes it easy to share the parts that people do want the same. Where I work we have slowly but surely come to an agreement on most of our git aliases. That's why we built [fresh] a similar tool to allow us to share the parts we want to. [fresh] allows us to easily override anything we don't like and keep the parts we do like up to date. My [freshrc] file is an example of mixing other peoples aliases and bin files with a collection of my own config. [fresh]: https://github.com/freshshell/fresh https://github.com/freshshell/fresh [freshrc]: https://github.com/twe4ked/dotfiles/blob/master/freshrc https://github.com/twe4ked/dotfiles/blob/master/freshrc