ngs

Thanks! I think it's about alignment of the project and how you think. If it won't be it this time, I'm working on the user interface of Next Generation Shell now and I would like to encourage you to revisit the project once that is done. Plan: https://github.com/ngs-lang/ngs/wiki/UI-Design https://github.com/ngs-lang/ngs/wiki/UI-Chain-Design Tldr: interactive objects on the screen, each interaction results "interaction record" (structured data about what happened), semantic understanding of what's happening, record/replay facility.

Hi. Author here. The biggest difference between NGS and other shells is the UI. It's work in progress. Ideas are at https://github.com/ngs-lang/ngs/wiki/UI-Design Another big difference is that NGS is a language designed ground up for DevOps-y tasks. The result, in my subjective opinion, is clear and concise scripting. That's due to better fit between the language and problems being solved. Edit: Python for example "doesn't like" functional programming, while NGS supports it and using map() and filter() is idiomatic. Edit 2: explanation why UI takes so long. That's because it is being implemented mostly in NGS itself so the language must be in shape (and now it is but it took time).

I would like to make my DevOps colleagues more productive and less frustrated. I'm actually already doing it, it's just way slower when you can't do it as a full time job. I started working on Next Generation Shell in 2013. I have the programming language in quite a good shape and we use it at work. I'm working on the UI now. The main idea of the UI is to get rid of telegraph-style communication paradigm of sending text and receiving text. We can actually use the whole screen now. We have text editing using full screen since 1976 (vi) but classical shells are ignoring this capability till this day. It's time to stop treating outputs of programs as if they are still printed on paper, allowing zero interactivity. https://github.com/ngs-lang/ngs/wiki/UI-Design https://github.com/ngs-lang/ngs/wiki/UI-Chain-Design Have a nice day!

Next Generation Shell because I refuse to believe that UI that is limiting the interaction to single line is the pinnacle of UX that we can have today. Terminals introduced cursor movement feature in the 1970s. Bill Joy responded with releasing vi in 1976. Text editing as we know it today was born. It used ... the whole screen! How the shell responded to this new feature? It largely didn't. Back to NGS. The programming language is in a good shape. Working on the UI. https://github.com/ngs-lang/ngs/wiki/UI-Design

Next Generation Shell. As a shell, it's a programming language and a UI. Half baked: programming language - pretty much done, we use it at work; UI - just starting to work on. Ananlysis of what's wrong with current shells' UIs and how to fix it - https://blog.ngs-lang.org/2023/09/30/ui-in-ngs/ Project - https://github.com/ngs-lang/ngs Any help would be appreciated of course :)

I might have issues later. For now, in Next Generation Shell peg/leg parser is doing fine (with limited scripting around to avoid repetition). https://piumarta.com/software/peg/ https://github.com/ngs-lang/ngs/blob/bdfb2fd70162cd7183ac8d4...

Here is my take on pattern matching. Tldr: generalize. https://github.com/ngs-lang/ngs/wiki/UPM-Design

Prepared a comparison to Next Generation Shell here: https://github.com/ngs-lang/ngs/wiki/Hush-vs-NGS On one hand we are on it since 2013 so there is "more" but I would actually like to highlight the difference in OOP and functional approaches: types, inheritance, multiple dispatch.

Thank you! For scripting, it is significantly better than bash (at least for most of the cases that I have). The interactive part is not implemented yet but it is planned to be quite different from the dominant decades old approach. The plan is at https://github.com/ngs-lang/ngs/wiki/UI-Design

NGS looks interesting as a Bash alternative. https://github.com/ngs-lang/ngs

Hello. Author of Next Generation Shell here. Good to see the attempt to fix the shitty user experience that is decades old. More NGS perspective on the UI - https://github.com/ngs-lang/ngs/wiki/UI-Design

Nice... but how you fix the way something fundamental as the way `if` works in bash? Each `if` is a bomb. `if grep -q ...;then ...;else ...;fi`. Two branches for three possible exit codes. Given a long script and big amount of output, you will miss the error message such as "file not found" and the execution will peacefully continue into the else branch. Things like the above motivated me to create Next Generation Shell. Edit: hint - yes branch, no branch, exception. More about motivation: https://ilya-sher.org/2020/10/31/bash-or-python-the-square-p... Project: https://github.com/ngs-lang/ngs

Depending on your exact needs, you might also want to try Next Generation Shell. It's a fully featured programming language for the DevOps-y stuff with convenient "print JSON" switch so "ngs -pj YOUR_EXPR" evaluates the expression, serializes the result as JSON and prints it. Disclosure: I'm the author Project link: https://github.com/ngs-lang/ngs Enjoy!

Hi. Author of Next Generation Shell here. Totally agree. Also UI of the shell is stuck and ignores pretty much everything that happened in last decades. Here is my plan for the UI: https://github.com/ngs-lang/ngs/wiki/UI-Design Edit: but I do try to keep interoperability with existing bullshit.

Powershell is available on Linux. Albeit it doesn't always play too nicely with existing CLI tools. There are also other typed shells that appeal to yourself which aren't Powershell but do have behaviours similar to Powershell and which do play a lot more nicely with the wider Linux / UNIX ecosystem: - murex https://github.com/lmorg/murex - Elvish https://github.com/elves/elvish - NGS https://github.com/ngs-lang/ngs I'm the maintainer of murex so happy to answer any questions on that shell here. I do know the the maintainers of Elvish and NGS pop on HN too.