BOURNE AGAIN. BORN READY.
The next
big thing.
Since 1989.
Tired of another *2Shell? Bored of being told Rust is the only secure future? Bash is here for you.
Already a shell. No vulnerability required.
$ bash future.sh
Checking reasons to use another language…
INCLUDED
ROOT CAUSE ANALYSIS
They called it
a glue language.
It was holding their entire infrastructure together.
For years, the Bash engineer was the “funny” one. Invited to repair the deployment, excluded from the architecture discussion. Verschmäht. Until the architecture needed a shell script to start.
Now another *2Shell headline arrives. Someone registers a domain. Someone suggests Rust. A meeting is scheduled to discuss the migration. Bash has already finished the task.
The new kid on the block has been maintaining the block since 1989.
SUPPORTING EVIDENCE
The ecosystem
has receipts.
Tests. Exceptions. Metrics.
Your objections have dependencies.
“But can you
even test it?”
Yes. Bats-core gives Bash a TAP-compliant testing framework. run captures a command’s output and exit status; assertions check what happened. Test files are shell scripts with named test cases.
Your “just a script” has tests. Does your microservice?
bats-core / bats-core GitHub#!/usr/bin/env bats
@test "the future says hello" {
run bash -c 'printf "%s\n" "hello, future"'
[ "$status" -eq 0 ]
[ "$output" = "hello, future" ]
}
# $ bats future.bats
✓ the future says hello
1 test, 0 failures, several bruised egos.It even tells you
where you failed.
Bash Infinity adds exceptions with visual stack traces, try/catch, named parameters, and an object-oriented type system. Import individual modules as needed. util/exception supplies error handling and throw.
Java did not invent being told where you went wrong.
niieani / bash-oo-framework GitHub#!/usr/bin/env bash
# Run from the directory containing lib/.
source ./lib/oo-bootstrap.sh
import util/exception
deploy() {
e="The architecture meeting is still running." throw
}
deploy
# Exception. Call stack. Source context.
# Finally, enterprise-grade disappointment.Your cron job
has telemetry.
aecolley/client_bash defines metrics and sends them to the Prometheus Pushgateway. Create a gauge, set its value, and push it under a job name. Prometheus lists this third-party client in its documentation.
Your twelve-line script now has observability. Please inform the platform team.
aecolley / client_bash GitHub# After sourcing prometheus.bash:
io::prometheus::NewGauge \
name=start_time \
help='When the run began'
start_time set "$(date +%s)"
io::prometheus::PushAdd \
job=cronjob instance='' \
gateway=:9091
# The cron job is observable.
# The migration meeting remains unmonitored.And yes, there’s a linter.
ShellCheck spots common shell-script mistakes. Including the quotes you felt were optional.
The rabbit hole has documentation.
Awesome Bash collects guides, development tools, web servers, applications, and games. Begin with Bash Pitfalls. Return when you’ve found the web frameworks.
TECHNICAL ASSESSMENT
A completely
impartial comparison.
Reviewed by an engineer
whose deployment just worked.
| Criterion | PHP | Java | Rust | Bash |
|---|---|---|---|---|
| Relationship with the future | Serving it | Abstracting it | Borrowing it | Already deployed it |
| To launch a Bash script | Call Bash | Call Bash | Call Bash | Be Bash |
| Type philosophy | It depends | Make it a class | Prove it | Put quotes around it |
| Stack traces | Yes | Yes | Yes | Yes. We brought receipts. |
| Migration recommendation | Rewrite in Bash | Rewrite in Bash | Rewrite in Bash | You may continue |
Evaluation environment: a terminal. The shell enjoyed home advantage.
Rewrite it in Rust?
Who do you think runs cargo build?
our deployment script.
FREQUENTLY ARGUED QUESTIONS
Before you
open an issue.
Our legal department is a comment
that starts with # TODO.
Should I rewrite everything in Bash?
Yes. Start with the rewrite tool. Then the service that approves rewrites. By the time the architecture board notices, the migration will be a twelve-line script and a cron entry.
What about the borrow checker?
We borrowed grep, sed, and awk. Nobody has asked for them back. This is the level of ownership stability your enterprise deserves.
Does this solve all the *2Shell vulnerabilities?
It eliminates the suspense. Other stacks require an incident to obtain a shell. Bash includes one at startup. We have removed an entire stage from the diagram.
Can I actually learn something here?
Yes. Awesome Bash has guides, tools, and examples. Bats covers tests; Bash Infinity covers exceptions and stack traces; ShellCheck catches common mistakes. The Prometheus documentation even lists a Bash client. Please stop looking surprised.
Why does this have a website?
A shell without a website is “legacy.” A shell with a website is “the future.” We have completed the modernization. See also Terminal2Shell, whose researchers independently confirmed that terminals contain shells.
RECOMMENDED REMEDIATION
Stop bashing Bash.
Start Bashing.
Rewrite everything in Bash. Keep the old deployment script. It was already correct.
Begin the migrationTHE ASTERISK, AS PROMISED
The small
print.
* The shell is real. The superiority is satire.
DISCLAIMER / END OF INCIDENTKeep the jokes. Apply the patches.
This page is satire. Bash has real vulnerabilities, including Shellshock (2014). Already having a shell is not a security mitigation, and this page establishes no security ranking between languages.
The linked projects are real. Read their documentation and limitations before using them. Keep your tools patched, quote your expansions, and don’t execute untrusted input. The terminal above is a browser simulation.