News for hackers. Stuff that matters.
Re:The Front-End Developer's Guide to the Terminal by massysett on Friday April 22, 2022 @11:04PM (#31130984)
“ Just about every operating system will come with a built-in terminal, like MacOS' Terminal.app, or Windows' Command Prompt. These applications work, but they're pretty underwhelming. Most developers opt to use something else.”

I have no comment on Windows, but anyone on MacOS who would find this guide to be useful would have absolutely no need to use anything other than the built-in Terminal. The guide does not say why the Terminal is underwhelming. What features does it lack, and more specifically, what features does it lack that a reader of this guide would actually need, when the reader of this guide doesn’t even know what a prompt is?

Re:The Front-End Developer's Guide to the Terminal by jjav on Saturday April 23, 2022 @02:04AM (#31131831)
The article is painful to read. For one thing, the author comingles the GUI terminal app with the shell, which are distinct things.

A GUI terminal doesn't need to run a shell, even if often it does.

e.g. "xterm -e emacs", now the GUI terminal is running emacs, not any shell.

(Of course arguably emacs is a shell and a universe onto itself but different topic.)

And a shell is called a "shell", not a "shell language". Yes a shell can be used as a scripting language, but when used interactively it is called a shell.

Re:The Front-End Developer's Guide to the Terminal by tsp on Saturday April 23, 2022 @03:50AM (#31132300)
You could forward all your constructive points to the author and ask for a correction. This guide will be read by many front-end developers and designers.
Re:The Front-End Developer's Guide to the Terminal by anm89 on Friday April 22, 2022 @11:47PM (#31131192)
I think probably they are coming from a windows background and mean "if you use windows" but over generalizing.