On 2026-10-24 05:59, c186282 wrote:
KSH and BASH are "mostly compatible". Minor diffs but
nothing hard to get around. Anything you can do in KSH
can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
In article <11bhv61$1bjd2$2@dont-email.me>,
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
On 2026-10-24 05:59, c186282 wrote:
KSH and BASH are "mostly compatible". Minor diffs but
nothing hard to get around. Anything you can do in KSH
can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
I think you're taking Speedy way too seriously here. All of your points
are valid, of course, but it should not be necessary to respond to the
troll.
BTW, you assert that there are (many) features of Ksh that are not (yet) present in bash. I'm not doubting you, but I am curious about examples.
It seems to me that if you assert something like that, you should give examples.
On 2026-10-24 14:10, Kenny McCormack wrote:
In article <11bhv61$1bjd2$2@dont-email.me>,
Janis Papanagnou˙ <janis_papanagnou+ng@hotmail.com> wrote:
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
I think you're taking Speedy way too seriously here.˙ All of your points
are valid, of course, but it should not be necessary to respond to the
troll.
Oh, I didn't knew that he's considered a troll. His post looked just uninformed, or opinionated, not trollish.
BTW, you assert that there are (many) features of Ksh that are not (yet)
present in bash.˙ I'm not doubting you, but I am curious about examples.
It seems to me that if you assert something like that, you should give
examples.
Mind that his post says "Minor diffs"; and I was not (not primarily) addressing the absolute number of features but those features that
are hard(er) or in practice impossible [based on existing functions]
to substitute. Off the top of my head I had been thinking of discipline functions, or the "type system" - these are very closely embedded in
the shell.
Note that while these features are probably not widely used there's
also many often used details I used, functions and options, that Bash
doesn't have as I noticed over the time. I've occasionally mentioned
those in some posts that where about such functionality, but I'm too
lazy to create a list or something, which would require to re-test
every features whether one or another has meanwhile been implemented;
that would be too much effort.[*])
Janis
[*] After finishing writing the post I remembered that we could ask
a search machine AI, but strangely it had no or found any substantial information, not even the obvious examples; so we have to rely on the
experts or own experience here.
In article <11bhv61$1bjd2$2@dont-email.me>,
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
On 2026-10-24 05:59, c186282 wrote:
KSH and BASH are "mostly compatible". Minor diffs but
nothing hard to get around. Anything you can do in KSH
can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
I think you're taking Speedy way too seriously here. All of your points
are valid, of course, but it should not be necessary to respond to the
troll.
BTW, you assert that there are (many) features of Ksh that are not (yet) present in bash. I'm not doubting you, but I am curious about examples.
It seems to me that if you assert something like that, you should give examples.
On 10/24/26 12:53, Janis Papanagnou wrote:
On 2026-10-24 14:10, Kenny McCormack wrote:
In article <11bhv61$1bjd2$2@dont-email.me>,
Janis Papanagnou˙ <janis_papanagnou+ng@hotmail.com> wrote:
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
I think you're taking Speedy way too seriously here.˙ All of your points >>> are valid, of course, but it should not be necessary to respond to the
troll.
Oh, I didn't knew that he's considered a troll. His post looked just
uninformed, or opinionated, not trollish.
˙ Thanks, I think˙ :-)
˙ I never 'troll' - just relate MY experiences and what
˙ I've learned from them. I had my own path, own needs,
˙ my own 'environments', starting in the punch-card days.
˙ But what served ME best may not be what served YOU, what
˙ I learned may not be what YOU learned.
˙ A great purpose of groups like these is to bring in
˙ a LOT of experiences and perspectives. You MAY find
˙ something compatible/useful in all the diverse advice.
˙ I don't pretend to know-it-all, nothing close (though
˙ a few, well, SAY they do :-)
˙ As said elsewhere, "NEED" eventually supersedes all else.
˙ Earlier on, all the shells maybe started with a narrow
˙ 'vision' but HAD to include capabilities the other people
˙ put in. Sometimes the additions were neat/clear, sometimes
˙ not so much, but they're THERE.
˙ A sort of 'functional convergence' due to NEEDS.
˙ Anyway, I reject 'religions' built around shells or
˙ langs and such. For each need, pick the best tools
˙ and approaches. "Best" - sometimes that's what most
˙ harmonizes with YOUR brand of thinking.
[...]
On 2026-10-26 05:28, c186282 wrote:
On 10/24/26 12:53, Janis Papanagnou wrote:
On 2026-10-24 14:10, Kenny McCormack wrote:
In article <11bhv61$1bjd2$2@dont-email.me>,
Janis Papanagnou˙ <janis_papanagnou+ng@hotmail.com> wrote:
On 2026-10-24 05:59, c186282 wrote:
˙˙ KSH and BASH are "mostly compatible". Minor diffs but
˙˙ nothing hard to get around. Anything you can do in KSH
˙˙ can be done in BASH.
This is not correct. While Bash has over time adopted quite
some features from Ksh - but sadly needed often far too many
years for that - there's still a lot substantial functions
in Ksh that Bash has not implemented (or substituted by some
equivalent feature).
I think you're taking Speedy way too seriously here.˙ All of your
points
are valid, of course, but it should not be necessary to respond to the >>>> troll.
Oh, I didn't knew that he's considered a troll. His post looked just
uninformed, or opinionated, not trollish.
˙˙ Thanks, I think˙ :-)
˙˙ I never 'troll' - just relate MY experiences and what
˙˙ I've learned from them. I had my own path, own needs,
˙˙ my own 'environments', starting in the punch-card days.
(I've still a block of punch-cards in the cellar, so I've got an
impression where you're coming from.)
˙˙ But what served ME best may not be what served YOU, what
˙˙ I learned may not be what YOU learned.
Oh, in my previous reply I said something like that; that it's
fine if it serves you in your private contexts.
A discrepancy might appear when you are working in a larger area
with rules that are not tailored to your personal likings but to
experiences from a larger (or another) group of persons.
˙˙ A great purpose of groups like these is to bring in
˙˙ a LOT of experiences and perspectives. You MAY find
˙˙ something compatible/useful in all the diverse advice.
˙˙ I don't pretend to know-it-all, nothing close (though
˙˙ a few, well, SAY they do :-)
Oh, I'm completely fine with that. - If statements are formulated
as opinions, what else can we do than agree to those or disagree.
A problem, though, is, when opinions are stated as facts, and if
statements are even wrong, then they should be corrected. (Or
clarified if it was just a communication or expression problem.)
˙˙ As said elsewhere, "NEED" eventually supersedes all else.
˙˙ Earlier on, all the shells maybe started with a narrow
˙˙ 'vision' but HAD to include capabilities the other people
˙˙ put in. Sometimes the additions were neat/clear, sometimes
˙˙ not so much, but they're THERE.
˙˙ A sort of 'functional convergence' due to NEEDS.
˙˙ Anyway, I reject 'religions' built around shells or
˙˙ langs and such. For each need, pick the best tools
˙˙ and approaches. "Best" - sometimes that's what most
˙˙ harmonizes with YOUR brand of thinking.
(Unfortunately language topics are often presented with religious
fervor.)
˙ My first computer was a PDP-11. Great unit.
˙ But still remember having to submit my card
˙ stack (DON'T drop it !) to the IT overlords.
˙ Helped a bit if you offered them 'gifts'.
On 2026-10-26 08:38, c186282 wrote:
[...]
˙˙ My first computer was a PDP-11. Great unit.
˙˙ But still remember having to submit my card
˙˙ stack (DON'T drop it !) to the IT overlords.
Corrupted data (if you've dropped it)...
˙˙ Helped a bit if you offered them 'gifts'.
...and corrupted people?
Janis
PS: The nastiest thing I've encountered with the
card deck was that a friend exchanged all my cards
which carried the word 'BEGIN' with cards carrying
the word 'SADAT' - just as a hilarious play with
words WRT two international politicians back then.
Not so funny for me when I noticed all the syntax
errors and had to wait another hour for the next
batch run.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:20:34 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |