What is better about this tool than PowerShell?

The README doesn't mention it at all, just that the tool is inspired by PowerShell.

Nothing. Lets be realistic.

Even if it goes mainstream it will be decade behind PowerShell in conceivable future.

While I appreciate the enthusiasm for developing shell, nothing usable here in years to come IMO when I can just use pwsh.

This reflects China's industrial strength, but it is not clear whether such small progress has practical value.In a word, it's better to work hard than not.

Sturgeon itself does not need to get any compensation, it is not human, no human rights.

The construction of the dam can bring a lot of immediate benefits, which is insignificant compared with the ecological damage caused, because if the economic development is not good, the environmental pollution will only be more serious, and the phenomenon of survival through predation of wild animals will only be more common.

Maybe it's just because people who love to eat mushrooms have better health habits.

With GraalVM, you can compile all JVM languages into binary files to run, including Python.

There are many other scripting languages to choose from, such as JavaScript，Ruby, Kotlin and Groovy.

Of course, you can also use Java，Scala, Clojure and so on.

Programming is not some very special skill, so that the question can be described as: how to learn scientifically and efficiently?

You can find a certain book about learning, which must be backed by sufficient scientific evidence, and then you can get more relevant content by using Amazon book recommendations, and the references in the back of this book to gradually acquire the latest knowledge in this area.

Of course every industry has some distinctive experiences or informal rules, but those things are often not the way to learn, but one of the materials to learn.

And don't expect anyone to give you the best study plan, because studying is a very individual thing, don't try to copy other people's experiences.

Reading relevant research gives confidence and allows one to avoid a lot of obvious mistakes, but it doesn't mean one can find a panacea, hard work is necessary.

thanks

Of course, only with reflection can we make progress. It's good to have some kind of automation mechanism to assist this process.

I believe that every software engineer who has introspective practice will have such an idea, which is not surprising.

This may be called

* Evidence based software engineeringg

* Empirical or experimental software engineering[^1]

Most people don't think about these things at all.

They think the rules of thumb are natural.

At present, I don't follow the latest research, but there are several famous books, which I recommend here.

- Making Software:What Really Works, and Why We Believe It

- Object-Oriented and Classical Software Engineering, 8th Edition

- Facts and Fallacies of Software Engineering

Most of the passages in those sources above are supported by detailed evidence, so following those well-marked references should lead to the latest content, except that I don't have time to do it, so I've put it aside for now.

Although this book is not a rigorous academic style, it does discuss issues related to it.

- The Problem with Software:Why Smart Engineers Write Bad

It should help you.

[^1]:https://stackoverflow.com/questions/1835059/what-is-evidence...

Strongly agree with you that there are two ways to significantly and inexpensively improve programming skills.

1. read books written by experts, especially those with good reviews. These books are often categorized as software engineering or software development methodologies. If you find one of these books, then go to sites such as Amazon to see the relevant recommendations, and gradually you can find almost all of them. 2. read the recognized good source code. This is hard, but necessary.

Then it needs to be accompanied by practice: use what you have learned above consciously in practice, so that you can consolidate this knowledge and even you can build on it to gain more specific insights.

Low cost means: no need to create a special environment and no need to be overly dependent on others.

Recognizing the problem is the first step in solving it. It's good that you are dissatisfied with yourself and have specified the reasons for your dissatisfaction.

But since the problems you gave are so specific, it is obvious that the solution is to solve them first.