I understand that for some people facts aren't that interesting and all that counts is fearmongering and conspiracy theories, but please, do some thinking sometimes.

If you have closed source software that contains hardcoded keys, one of which is labelled as NSAKEY in the debug-build, coming from a company that is factually known to cooperate with the US government under the obligation of NSLs and give at least the FBI and NSA access to their users data.

No, the fact that there are hardcoded keys isn't suspicious at all. How else would you implement digital signing of software? That's what these two keys are, they are public keys for software signing. Why there are two of them, and why one has 'NSA' in its name? Back in the days there were cryptography export restrictions (on request of NSA), you couldn't export strong algorithms outside the USA, so software often had two versions, with stronger and weaker crypto. As you can guess, one of these keys is weaker and one is stronger. Now you understand why this key has 'NSA' in its name, this key was needed because of restrictions required by NSA.

Okay, let's say that Microsoft are dirty liars, and they created second key just as digital signing backdoor for NSA. In that case you should ask yourself, why would they do that? Why would they create second key when they could just give their own key to the NSA and not cause any suspicion? Also, ask yourself why in bloody hell NSA would need backdoor in such uninteresting module of Windows? It's not like it would gain them any way to remotely access the Windows PC.

Please, do some research, don't base your opinions on your feelings and prejudices. Sadly, I don't expect that I will convince you, people with "wake up sheeple!" mentality aren't the ones that like being proven wrong.

http://web.archive.org/web/20000520001558/http://www.microsoft.com/security/bulletins/backdoor.asp

https://news.ycombinator.com/item?id=9292749

It may be interesting for people exploring non-conservative programming paradigsms. APL is very interesting (and different) language, but it's heavy use of unicode symbols is off-putting for most people. That's the reason why J and ELI exist, they both attempt to make the language more accessible by restricting themselves to ASCII character set.

Finally, I've been waiting for this for years. Unfortunately, PowerShell still has many problems, it's slow, really verbose and OO shell is totally foreign concept for most users including me. IMHO most users were expecting something simpler, like Hamilton C shell or even TakeCommand.

Please, don't be spreading FUD. This variable was introduced in 1999, in Windows NT4 SP5, and there is totally no evidence that it's a backdoor. This symbol was introduced 16 years ago and since then nobody showed the way how is this "backdoor" supposed to work (in technical sense), there are only suspicions and accusations. Security researchers had freaking SIXTEEN years to show how exactly this backdoor is constructed. The only reason why people say that there's a backdoor is the name of symbol in library, three letters, nothing more.