[usrbinbash]

> "minimal"

Here is what a minimal shell prompt looks like:

    $

Here is another one which only uses the shells own facilities:

    current-directory@hostname $

Running a complex piece of software every time the shell needs to display it's prompt, is not "minimal", regardless of how fast and well written said piece of software is.

[daliusd]

I still think minimal is appropriate in this case as it shows only what’s relevant in the context.

[INTPenis]

You're missing the point. It runs every time you show the prompt. Anything that does that is not minimal and it increases the risk of failure.

Some things that you use regularly should be kept as minimal and as stable as possible. To me that includes the shell prompt, editor, browser for example.

[daliusd]

I am cli/vim guy - that’s my daily tools. Starship is very stable and it is useful for me. The only problem I have experienced is with custom extension I wrote myself (problem was slowness not stability).

[usrbinbash]

That's all well and good, but has nothing to do with my argument.

If you need to invoke a program for every prompt, when the alternative is to just let the shell do it's thing, it's no longer "minimal", period.

[daliusd]

Well, we are arguing about semantics. You say that minimal means that it must be functionally minimal. I say that minimal UX is valid meaning as well.

[usrbinbash]

> Well, we are arguing about semantics.

No, we are not. "minimal" has a defined meaning, and "minimal" and "minimalism" as a design philosophy are not the same.