It's a tool.

Some chefs like to spend hours sharpening their knifes with wet stones. Others are just going to run it through a power sharpener and get on their way.

I like to focus my craft in places other than the terminal.

Different strokes I guess. Personally I think any time spent tinkering with the shell is a waste of time: a basic, zero-customization bash is just as good at doing things for me as a shell that I've messed around with the settings on for ages. So I don't waste time on customizing my shell because it provides no value to me, while those who get value can spend the time. We both win.

there's some nuance to this. people might want to spend minimal time hacking on their shell and more time hacking on things they find interesting that are not related to shell setup (and also not webshit). besides even if its webshit, what makes you say shell setup hacking is more or less interesting compared to webshit hacking. the term webshit itself implies you view it as less interesting than shell setup -- fair if thats your pov, but doesnt make it intrinsic.

> important webshit to build

hackernews: where a large portion of programmers are considered inferior because of the domain they work in (the domain where hackernews also lives)

Time is finite.

I could spend that time tinkering with the internals of an ad-hoc informal system cobbled together in the 1970s and held together by spit and glue.

Or I could just not do that.

Also, the implication that fiddling with shell scripts is somehow a better engineering/programming practice than web programming is laughable at best.

Hacker News: Where the hackers don't want to think about the code required to build the webshit nor the command-line nonsense used to write it, because the agents will take care of all that.