HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ngs-lang
ngs
C2016–2025
ngs-lang / ngs

ngs

Next Generation Shell (NGS)

11Distinct people
54Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Next Generation Shell (NGS)

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:59:04 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year54 dated mentions

Observed mentions: 2016-04-21 10:54:15 UTC to 2025-05-04 03:32:47 UTC.

01020302016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 27 mentions; 0 submissions, 27 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC312
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC404
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC413
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC27027
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC808
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

4 sources
Hi. Author of Next Generation Shell here. Here is my take on bash vs Python and friends. I am frustrated by both. bash - domain specific language and huge library (CLI utilities) and lets you get the job done but not a language I would like to use (syntax, error handling, very limited structured data support). Python - okayish as a language but doing domain specific things (working with files and processes) is so much more verbose than bash. My solution in NGS - have a high level, modern language with the typical goodies like ... exceptions (wow, completely new concept!) and the language is still domain specific. Working with processes for example has it's own syntax and is much more concise and straightforward (stole bits from bash). Right now the project has the language, which is useful enough to write scripts (which we do at work). Re
Read the rest
garding contribution to the project, my idea is that as much as possible should be in NGS language (as opposed to the lower level C). The UI will be implemented completely in NGS, allowing contributing to the project using the same language you are writing your scripts in. https://github.com/ngs-lang/ngs As a side note, while the UI is not there yet, I do plans for it which include interaction with objects on the screen as opposed to current "here is your dump of text" situation... and in general be more considerate of the user. https://github.com/ngs-lang/ngs/wiki/UI-Design
In Writing Safe Shell Scripts (2019)
> not learning enough bash to use it properly and then complaining about it By the same logic, whoever prefers C over assembler, Python over C, etc just doesn't understand the latter language enough. I think this logic is flawed. > google chrome windows I wouldn't accept a shell that works only in a browser. If you would take a minute to actually look at https://github.com/ngs-lang/ngs/wiki/UI-Design , it reads: "Ability to support several i/o modules", with sub-items "Console module" and "Later: web module" > Bash is more than fine. Depends on the situation and task at hand. For me, most of the time, bash is not fine. I do have a bunch of bash scripts because for their task they are the best solution in my opinion... and that's what makes me sad. That is not fine. > You can't expect to get correct behavior without understanding your tool
Read the rest
s and your shell. By that logic, whoever complains about any flaws in a language (error handling and missing generics in Go come to mind) just doesn't understand the language. I think this logic is flawed. > You can't expect not to do error-checking and corner-case-checking and still have stuff working 100% of the time. I don't. That's bash and that is how it works... and I don't like it. Looking at two alternatives: exceptions vs error codes checking. I strongly disagree with error codes checking approach. I do prefer (in most of my scripts) uncaught exceptions (which would terminate the script) and smaller code. The alternative with error codes checking is either have substantially larger code or incorrect behaviour. I strongly disagree with the trade-off that bash makes. > can you really blame it on bash There is a lot of crap going around. Not everything is on bash.
In “Use Dumb Shell, Don’t Reinvent the Wheel”

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.