Microsoft PowerShell now on Apple macOS and Linux
Ping!
The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.
If you want on or off the Mac Ping List, Freepmail me
Posted on 01/12/2018 6:11:41 AM PST by dayglored
Abuse? What could go wrong?
Sorry, I don't see the point of having yet another completely incompatible shell. Why not just join the rest of the world and make tools that play well with others?
The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.
If you want on or off the Mac Ping List, Freepmail me
Again, the non-Apple user chimes in to make claims about that he knows less than zero about.
In fact I used it quite a bit when I had an MBP.
For a person who does any kind of development it's syntax is ridiculous. It's no easier to use words over symbols. Being different for the sake of being different is counter productive.
For Example
AppleScript
set theDelimiter to ","
set theString to "The guy went to the store, and then to the cafe"
set originalDelimiters to Applescript's text item delimiters
set Applescript's text item delimiters to theDelimiter
set splitText to theString's text items
set Applescript's text item delimiters to originalDelimiters
PowerShell
$TheString = "The guy went to the store, and then the cafe"
$SplitString = $TheString.Split(",")
I guess it's best for you to stay with Apple Products.
off topic- but got this in an email the other day from a relative who has a mac- seems there is some concern about someone using mac os somehow having stolen personal info- Don’t kow the details, I don’t use mac- but it looked pretty bad-
Another way to look at it is if you have a heterogeneous environment with servers and computers running Apple, Linux and Microsoft, you can use just one command set to manage and automate tasks in PowerShell. On all of them!
I wish fan bios would see the utility in that without kicking the OSs they don’t like just because.
PowerShell is software, not an OS. Chill out folks!
zeugma, this is Microsoft. I gather you haven't met.
Well, yeah. That was a pretty dumb comment on my part.
Fruitfly was discovered in January 2017. It is spread by a Trojan or by physical access to the victim's computer. It was determined to have infected approximately 400 total Macs. That's it. To claim that "millions of images were stolen" is totally absurd and complete hype as it apparently was the work of a single person a pervert, named Phillip R. Durachinsky, who is now under arrest and being prosecuted.
When discovered in January, it was primarily found on Mac computers located in biological, chemical, genetic, and pharmaceutical laboratories in college, university, and commercial settings, hence the name "FruitFly" and was originally thought to be a commercial espionage effort. All infections have a phone home component that lead to a single server and the server was tapped by the discoverers and they found the approximately 400 computers that were reporting in/or were being watched. The location of the server was not known until the authorities located it in the possession of Durachinsky.
They have found he also has been running versions of FruitFly for Windows PC. . . and the higher number of claimed infections may be coming from those PCs, not Macs, because this is an Intel based code which the authorities claim has been in the wild for 13 years, yet Apple only switched to Intel based processors ten years ago and the earliest Apple Mac based version of FruitFly found was for OS X.9 Mavericks which was released only four years ago. Ergo, FruitFly probably has been around a lot longer on Windows machines. However, it should be noted that the code is only two lines long and WILL run on any Intel Mac that is OLDER than the Mavericks version. There is just no evidence that it did.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.