docs(FAQ): Why JS?

Author: jcs090218

docs/content/FAQ/_index.en.md

@@ -14,7 +14,7 @@ Here is a list of general frequently asked questions.
 The answer is **NO**.
 
 Eask builds native executable on every release, see our [release page](https://github.com/emacs-eask/cli/releases)
-to download it! However, Node.JS is required if you are going to develop Eask!
+to download it! However, [Node.JS][] is required if you are going to develop Eask!
 
 ## ❓ Who should use this tool?
 
@@ -33,32 +33,47 @@ repository!
 
 ## ❓ Why Node.JS?
 
-Node has better support on all kinds of terminal applications (compare to just
-the shell script)! Like colorful interface, entire npm community, etc. So you
-can build cross-platform software with fewer hassles! Especially after Microsoft
-had bought the NPM inc, and would likely support their own system well.
+[Node][Node.js] provides better support for various terminal applications compared to shell
+scripts. It offers features like a rich, colorful interface and access to the
+vast npm ecosystem, making cross-platform development more convenient. This is
+especially true since Microsoft acquired [npm][] Inc., likely ensuring strong
+support for their own systems.
 
-Cask does not seem to support Windows (no WSL) after version `0.8.6`. In the
-early versions, they have used Python, but due to the Python supports on Windows
-are just not as good as Node.JS.
+[Cask][] seems to have dropped support for Windows (while still supporting [WSL][])
+after version `0.8.6`. Earlier versions were built on [Python][], but [Python][]’s support
+on Windows has traditionally been less reliable than [Node.js][].
 
 See [issue #140](https://github.com/emacs-eask/cli/issues/140) for more information!
 
+## ❓ Why JavaScript?
+
+There are many languages I could use to build around Eask, so why did I choose [JavaScript][]?
+
+I have three reasons:
+
+- [JavaScript][] is easy to learn.
+- It offers excellent cross-platform compatibility, thanks to the [Node.js][] runtime.
+- I just happen to know [JavaScript][], and I’m comfortable with it.
+
+I also considered [Rust][] and [Common Lisp][]. However, [Rust][] was still relatively
+new when I started this project, and [Common Lisp][], while powerful, has a steeper
+learning curve and is often seen as somewhat outdated. So, I went with [JavaScript][].
+
 ## ❓ Why yargs?
 
-[yargs][] has a very wide community; and it has been used in many tools.
-It's cross-platform! And most importantly, this is one of the tools that
-work well on Linux, macOS, and Windows.
+[yargs][] has a large and active community and is widely used in various tools.
+It’s fully cross-platform and, most importantly, works seamlessly on Linux, macOS,
+and Windows.
 
-There is also the major difference compared with Eask and other alternatives.
-[Cask][], [makem.sh][], or [Eldev][] rely more on `batch` and `bash`. We chose a
-different route and would like to hand over heavy tasks to a high-level
-programming language, **`JavaScript`**. The development simply became easier,
-since we don't need to care about different types of shells anymore!
+One key difference between Eask and other alternatives is how they handle scripting.
+Tools like [Cask][], [makem.sh][], and [Eldev][] rely heavily on batch and bash scripts.
+Instead, we took a different approach by leveraging a high-level programming
+language-[JavaScript][]. This made development significantly easier, as we no longer
+need to worry about shell compatibility.
 
-The drawback is the NodeJS runtime, but we can simply pack the entire CLI
-program into an executable! That way we would not need to install `Node` and
-`npm` before using eask!
+The main drawback is the [Node.js][] runtime requirement, but we can mitigate this
+by packaging the entire CLI program into an executable. This way, users won’t
+need to install [Node][Node.js] or [npm][] beforehand to use Eask!
 
 # 🔍 Usage
 
@@ -166,8 +181,17 @@ Add the following code snippet to your Eask-file:
 <!-- Links -->
 
 [emacs-eask/archives]: https://github.com/emacs-eask/archives
+
 [Cask]: https://github.com/cask/cask
 [makem.sh]: https://github.com/alphapapa/makem.sh
 [Eldev]: https://github.com/doublep/eldev
 
+[Node.js]: https://nodejs.org/
+[npm]: https://www.npmjs.com/
 [yargs]: https://www.npmjs.com/package/yargs
+
+[WSL]: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
+[JavaScript]: https://simple.wikipedia.org/wiki/JavaScript
+[Python]: https://www.python.org/
+[Rust]: https://www.rust-lang.org/
+[Common Lisp]: https://lisp-lang.org/

docs/content/FAQ/_index.zh-tw.md

@@ -14,7 +14,7 @@ weight: 900
 答案是 **不**.
 
 Eask 在每個版本上構建本機可執行文件，您可以從我們的[發布頁面](https://github.com/emacs-eask/cli/releases)
-下載！ 但是，如果您要開發 Eask，那就需要需要 Node.JS！
+下載！ 但是，如果您要開發 Eask，那就需要需要 [Node.JS][]！
 
 ## ❓ 誰應該使用這個工具？
 
@@ -31,26 +31,39 @@ Eask 在每個版本上構建本機可執行文件，您可以從我們的[發
 
 ## ❓ 為什麼選擇 Node.JS?
 
-Node 對各種終端應用程序有更好的支持（相比 shell 腳本）！ 比如豐富多彩的界面，整個 npm 社區等等。
+[Node][Node.js] 對各種終端應用程序有更好的支持（相比 shell 腳本）！ 比如豐富多彩的界面，整個 [npm][] 社區等等。
 所以你可以更輕鬆地構建跨平台軟件！ 尤其是在微軟之後已經購買了 NPM 公司，並且可能會很好地支持他
 們自己的系統。
 
-在 0.8.6 版本之後，Cask 似乎不支持 Windows（無 WSL）。 在裡面早期版本，他們使用的是 Python
-但由於 Python 在 Windows 上的支持只是不如 Node.JS。
+在 `0.8.6` 版本之後，[Cask][] 似乎不支持 Windows（但支援 [WSL][]）。 在裡面早期版本，他們使用的是 [Python][]
+但由於 [Python][] 在 Windows 上的支持只是不如 [Node.JS][]。
 
 有關詳細信息，請參閱[問題 #140](https://github.com/emacs-eask/cli/issues/140)！
 
+## ❓ 為什麼選擇 JavaScript?
+
+我可以使用許多語言來建立 Eask，為什麼我選擇 [JavaScript][]？
+
+我有三個理由
+
+- [JavaScript][] 容易學習。
+- 得益於 [Node.js][] runtime，它提供了極佳的跨平台兼容性。
+- 我恰好了解 [JavaScript][]，而且用起來得心應手。
+
+我也考慮過 [Rust][] 和 [Common Lisp][]。然而，當我開始這個專案時，[Rust][]
+仍是比較新的語言，而 [Common Lisp][] 雖然功能強大，但學習曲線較陡，而且經常被視為有點落伍。因此，我選擇了 JavaScript。
+
 ## ❓ 為什麼選擇 yargs?
 
 [yargs][] 擁有非常廣泛的社區； 和它已經被用在很多工具中。 它是跨平台的！
 最重要的是，這是在 Linux、macOS 和 Windows 上運行良好的工具之一。
 
 與 Eask 和其他替代方案相比，也存在主要差異。[Cask][]、[makem.sh][] 或 [Eldev][] 更依賴於
-`batch` 和 `bash`。 我們選擇了一個路線不同，想把繁重的任務交給高層編程語言，**`JavaScript`**。
+`batch` 和 `bash`。 我們選擇了一個路線不同，想把繁重的任務交給高層編程語言，[JavaScript][]。
 開髮變得更加容易，因為我們不再需要關心不同類型的 shell！
 
-缺點是 NodeJS 的 runtime，但我們可以簡單地打包整個 CLI 程序變成可執行文件！ 這樣我們就不需要安裝
-`Node` 和`npm`！
+缺點是 [Node.JS][] 的 runtime，但我們可以簡單地打包整個 CLI 程序變成可執行文件！ 這樣我們就不需要安裝
+[Node][Node.js] 和 [npm][]！
 
 # 🔍 用法
 
@@ -150,8 +163,17 @@ Error: Process completed with exit code 1.
 <!-- Links -->
 
 [emacs-eask/archives]: https://github.com/emacs-eask/archives
+
 [Cask]: https://github.com/cask/cask
 [makem.sh]: https://github.com/alphapapa/makem.sh
 [Eldev]: https://github.com/doublep/eldev
 
+[Node.js]: https://nodejs.org/
+[npm]: https://www.npmjs.com/
 [yargs]: https://www.npmjs.com/package/yargs
+
+[WSL]: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
+[JavaScript]: https://simple.wikipedia.org/wiki/JavaScript
+[Python]: https://www.python.org/
+[Rust]: https://www.rust-lang.org/
+[Common Lisp]: https://lisp-lang.org/