One of the upsides of the pervasive JS is that it often calls APIs that do useful things. If you take the time to capture and study those interactions, you can develop your own libraries and CLI tools that operate those useful APIs, too [0]. Then, you can think of "browser time" as an investment that begets more "terminal time." Also, if you stick with simple interfaces for your CLIs (e.g., read and write pretty printed JSON instead of inventing your own "human readable" formats), it's much easier to make your tools snap together like German nouns, like McIlroy intended [1].

[0] This is all subject to how much you care, of course. Not all automation is worth the hassle.

[1] His metaphor was actually garden hoses that screw together.