@maiyannah And that's why I always try to remember that the start of National Socialism was in cultivated victimhood and the blaming of Others as the great Cause and Nemesis.
Would be rather epic if Intel manages to create a foolproof backdoor into every PC with no way to prevent it from being abused (by the general public, let's be fair, it's more than likely already abused by the TLA's).
@maiyannah mysql_query has been deprecated for a long time and has in fact been removed in 7. Doesn't mean of course that you won't come across it sometimes.
@moonman There are some good ideas in there. The whole concept of returning objects and formatting them in different ways is interesting and if there is enough environment support for it (i.e. the whole OS uses it pervasively) it can work well. But due to legacy and MS not really being all that fan of hackability it simply doesn't get the support.
@ickster I think it's the difficulty of making stuff work with powershell that causes this. Probably the admin division of MS is a heavy pusher of it since it really benefits them but as a consequence they're the main people writing cmdlets.
Meanwhile unix shells are easy to make a program work for since they operate on the same stdin, stdout, stderr streams that most programs naturally use.
The downsides of incompatible formats between programs that unix suffers from are in practice mostly solved by people hacking stuff together. Powershell on the other hand is very much a cathedral system in that it requires some kind of central design and interfaces.
I would say that an approach like http://scriptcs.net/ is much better for scripting. For command line script bashing the ability to quickly execute F# programs could be much better. In command line script bashing in my experience you're using a mixed procedural / functional paradigm (for loops and pipes) and F# really isn't all too bad for that.
Powershell's solution is to focus on .NET assemblies instead of on programs. But using OO from powershell is awkward, it's possible but not as easy as from C#.
Meanwhile the scripting aspect of Powershell is both underdocumented and really rather awkward.
It feels like Powershell is trying to combine two things: exploratory bashing (i.e. writing for loops on the command line) and scripting and is succeeding at providing a pleasant environment for neither.
Verius (verius@community.highlandarrow.com)'s status on Sunday, 05-Nov-2017 09:44:47 EST
VeriusTo get auto completion for C# in Emacs install OmniSharp. To install OmniSharp install .NET targeting thingy then try to build. Then discover that there's some call to some kind of weird ass new powershell 6 method and try to install newest powershell. Figure out that to install newest stable powershell you need to download a few zips from MS and run powershell scripts in them as admin.
Windows is improving, it's becoming more like Linux. :P