编程与软件工程github.com
Bash Infinity：Bash 的标准库与脚手架框架
Bash Infinity: Standard library and boilerplate framework for Bash
2016 — 2018，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
Bash Infinity 是一个为 Bash 打造的标准库与样板框架，通过面向对象、异常处理、try/catch、命名参数等特性，把 Bash 扩展成接近完整编程语言的样子。它在 2016 和 2018 两次登上 Hacker News 首页，引发了对“Bash 到底该写多复杂”的长期争论。
为什么经久不衰：它代表了用工程手段驯服 Bash 的极致尝试，也集中体现了“脚本该不该写成程序”这一经典分歧，至今仍是 shell 脚本设计讨论的参照点。
HN 评论精选
项目 impressive 但语法负担使其不如直接用真正的编程语言
Bash 能做到这些实在令人惊叹，这个库几乎让 Bash 拥有了完整语言的所有特性。但我也怀疑它的使用场景：这些额外语法相当于要学一门新语言，那还不如直接用内置这些特性的语言。而且我需要 shell 脚本时通常是为了可移植性，会写 sh；需要更复杂的东西时，我会用真正的编程语言。
johnramsden查看英文原文
Pretty amazing what can be done with bash, and it looks very impressive. I can't believe all the features that were able to be put together to make using the library essentially give bash all the features of a full-featured language. However, at the same time I kind of wonder what the use case would be for this. With all the extra syntax it would basically be equivalent to learning a new programming language, at which point it just seems to make more sense to use languages that have these features baked in. While it looks like a really cool project, I could never see myself using it, as usually when I want to use a shell scripting language I want full portability, and end up writing in sh. When I want to write something more advanced I use real programming language.
引用 Google 风格指南：超过 100 行的脚本就该换语言
作为一个长期使用（和滥用）Bash 的人，推荐这份凝聚了大量经验的文档：Google Shell 风格指南——'如果你的脚本超过 100 行，你大概应该用别的语言来写'。
mrybczyn查看英文原文
As a long time bash user (and abuser), I will just point you to this document, which distills a lot of wisdom: https://google.github.io/styleguide/shell.xml "If you are writing a script that is more than 100 lines long, you should probably be writing it in something else"
担心引入框架带来的依赖管理负担
我用 Bash 不多，主要是写一些能在自己各台机器上跑的数据处理脚本。我不太敢用这样的框架，因为担心要在不同开发机器上管理更多依赖。大家用 Bash 写的东西，究竟复杂到什么程度才需要这样的框架？
gjstein查看英文原文
I suppose I only use Bash infrequently, but when I do it is normally in an effort to make scripts that I know will run on my various machines for data processing and the like. I am hesitant to use a framework like this (as exciting as it seems) because I fear it would mean managing more dependencies across my different development machines. What are people using Bash for that would require enough complexity that a framework like this becomes a godsend? Edit: typos.
需要这种复杂度本身就说明不该用 Bash
如果你需要这么复杂的东西，你一开始就不该用 Bash 来写。每当我希望有数组、真正的数据类型或真正的函数时，我就立刻停用 shell 语言。Shell 脚本只适合那些你本来就会在 Unix 提示符下亲手敲的命令——而这类事情很少超过几行，所以 shell 脚本也不该更长。
massysett查看英文原文
If you need something this elaborate, you really shouldn't be writing it in Bash in the first place. Anytime I find myself wishing I had arrays, or real data types, or real functions, I stop using shell languages immediately. Shell scripts are really only suitable for the exact same sorts of things I would type myself at a Unix prompt...and since those sorts of things are rarely more than a few lines long, shell scripts shouldn't be longer than that either.
历次讨论
同类还值得读
开源应用架构
The Architecture of Open Source Applications
《开源软件架构》（AOSA）是一本在线免费书，邀请知名开源项目的作者亲自剖析其内部设计，涵盖 SQLAlchemy、LLVM、Audacity、Apache、Bash 等系统。
编程与软件工程上首页 9 次 · 2011–2024aosabook.org编辑精选编程语言简史：简短、不完整且多半错误
A Brief, Incomplete, and Mostly Wrong History of Programming Languages
一篇以戏谑、故意不准确的方式回顾编程语言史的博客文章，用夸张轶事和讽刺定义串起 Lisp、C、C++、Java、JavaScript、PHP 等语言。
编程与软件工程上首页 8 次 · 2009–2021james-iry.blogspot.comSQLite 是如何测试的
How SQLite is tested
SQLite 官方文档页，系统介绍 SQLite 的测试体系：多种测试方法（TCL 测试、模糊测试、回归测试、静态分析等）和海量测试用例，展示了这个小型开源项目如何靠极致测试获得…
编程与软件工程上首页 8 次 · 2009–2025sqlite.org编辑精选高级编程语言（2009）
Advanced programming languages (2009)
Matt Might 的经典文章，按用途推荐“高级编程语言”：如果追求就业就选主流语言，如果追求表达力、学术研究或创业，则推荐 Haskell、OCaml、Scala 等函数式语…
编程与软件工程上首页 8 次 · 2009–2022matt.might.net我的 Forth 与栈机器经历
Yosefk - My history with Forth & stack machines
作者以亲身经历回顾了使用 Forth 语言和栈式机器的历程：既赞叹其简洁优雅、代码量小、可自举的优点，也坦率指出栈操作在实际编程中的痛苦，以及 Forth 社区文化中的问题。
编程与软件工程上首页 8 次 · 2010–2024yosefk.com编辑精选