Because bash is everywhere. Stability is a separate concern. And we know this because LLMs routinely generate deprecated code for libraries that change a lot.

▲

gaigalas 4 hours ago | parent [-]

This project runs on all shells, totally portable:

https://github.com/alganet/coral

busybox, bash, zsh, dash, you name it. If smells bourne, it runs. Here's the list: https://github.com/alganet/coral/blob/main/test/matrix#L50 (more than 20 years of compatibility, runs even on bash 3)

It's a great litmus test, that many have passed. Let me know when just-bash is able to run it.

▲

esafak 4 hours ago | parent [-]

I have no connection to coral or just-bash. Why don't you do it yourself and let us know, since you are familiar with it?

▲

gaigalas 4 hours ago | parent [-]

I've been working with the shell long enough that I know just by looking at it.

Anyway, it was rethorical. I was making a point about portability. Scripts we write today run even on ancient versions, and it has been an effort kept by lots of different interpreters (not only bash).

I'm trying to give sane advice here. Re-implementing bash is a herculean task, and some "small incompatibilities" sometimes reveal themselves as deep architectural dead-ends.

▲

esafak 3 hours ago | parent [-]

The project does not list portability as a concern. It's for agent use; they are not trying to re-use existing bash code.

▲

gaigalas 2 hours ago | parent [-]

Before, you said:

> they use it because there's a lot of training material.

Now, you say:

> they are not trying to re-use existing bash code.

Can't you see how this is a contradiction?

---

I'm sorry, I can't continue like this. I want to have meaningful conversations.

	▲	esafak an hour ago \| parent [-]
		Is English your second language? "They" refers to very different things here.