Russia does have fabs. The Mikron Group made the Elbrus-2SM processor. They can't do less than a 90nm process yet.

These are fabricated in Taiwan. You had best keep using your abacus for a while longer.

I don't see why there would be such a delay when the article says:

As for the "five years behind comment" (which was not anyone bragging but instead criticising), I suspect that the article mashed together two different quotes into one. In terms of performance (which put them between the i3 & i5), they are five years behind mainstream performance. But it is difficult to compare this and the other performance metrics because of the architectural differences. This isn't a x86 CPU, it is more of a hybrid design. It runs at a very low clock speed (800MHz) and it's power requirements (45W) are low for a 65nm process.

It's not really the important part of the story though. For some countries affected by US export restrictions, having an alternate supplier makes them better than nothing. This CPU will not make the company a household name in the West, but they will continue to have a market in the places that the big boys can't play.

If you have a need to recompile Powershell, it would be because it lacks something. What is it lacking? I understand that ideology is important and that open source is a reasonable thing to prefer, but that it not an answer to my question of what Linux does that Powershell does not.

I think that you have put way too much thought into this. It is just not important. The original comment was inaccurate and just not insightful. If it is so wrong to correct the examples offered, then perhaps it was equally wrong for the AC to make the original post in the first place as it serves no point other than to perpetuate the myth that the language is too verbose to use.

I do acknowledge your pedantry though.

Except the majority of people running Windows don't use Powershell, so *.ps1 files cannot be used as a mechanism to infect those systems with malware. And you can still use Powershell interactively without having to change the security. This only affects people who want to run script files.

And there is no one operating system that has every single security feature, let alone has them enabled by default. Just because OpenBSD doesn't have it, doesn't mean that it isn't a security feature on Windows.

Have you never heard of people getting the wrong impression of something? I have merely corrected the impression that Powershell will always be verbose where *nix is concise.

Yet I have already shown you that it has built-in short aliases for common functions (some which use standard Unix names), and you can add your own. For the long commands and parameters Powershell has tab completion that is miles ahead of bash as it works for parameters and values too.

When the initial remark was "I can do a lot more with old linux tools than powershell have ever had the capability of" and the grandparent said "If you know linux well enough, you have complete control over everything including the kernel", then short (and cryptic) command names is an underwhelming example to choose.

Who has been doing this? Scanning through the posts here shows a lot of nay-sayers who are obviously uninformed, but I don't see any people saying that Powershell can do things that Bash can't without offering an example. And even if they do, why don't you ask them for examples like I did?

In the meantime, I still have to keep asking what it is that Powershell can't do.

No, that would be secure-by-default. Sorry that is an inconvenience for you.

So you claim, but I have yet to hear of anything that can't be done in Powershell. Undoubtedly there will be something, but I think that most of the time when people make this claim it is because they just assume that it is the case. But when asked to back up the statement...

Well, we can see what has happened. Just further vague claims.

Those examples are wrong.

GNU/Linux copy command: cp
Powershell: cp

GNU/Linux delete command: rm
Powershell: rm

That's easy to do with set-alias. It already has built-in aliases for mv, cp, ls, cat, diff, echo, lp, man, ps, pushd, rm, wget and many more. Use get-alias to see the list of them.

For the other commands you listed, I use UnxUtils. It's a lot lighter than cygwin, although the versions are very old.

Once you get used to the naming system then it is quite intuitive. And if you don't know how to do something then it has some built-in mechanisms to make it easy to find out how to do things. For example, if you don't know how to import a CSV file, try get-help *csv* and it shows all the aliases and commandlets and pertain to CSV importing and exporting.

Then with tab completion you can Import-Csv - and press tab after the dash and view all the parameters of the command. If you choose -Encoding press space then press tab again and it displays the options just for that argument (the different encoding types).

So all that was found without having to look up help files. You didn't even need to look at get-help to see the list of commands. Just type *csv* and press tab and display the commands interactively.

So yes it is a verbose language, but that makes it easier to discover the commands to use.