Follow Slashdot stories on Twitter


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Comment Or the other reason.... (Score 3, Informative) 357

The fact the whole state is a river flood plain and only stupid people build homes in a river flood plain?

Global warming may have cause the weather pattern changes, but it does not change the fact that if you build in the low lands, you have to expect flooding because it will absolutely happen with a 100% guarantee.

Comment Re:Spoofing should work by whitelist (Score 1) 110

100% bs. they know where they are coming from.

When a VoIP call is made to a landline or cellphone number, the call travels for a portion of the time over the PSTN. The amount of time the call spends on the PSTN usually determines the price of the call (apart from the base charges for any VoIP to VoIP call).

At the point where it enters the PSTN, a process called address translation takes place. It means that the IP address is translated to the identifying phone number of the called party to complete the call. It is similar to the process used to convert email IDs and website links to IP addresses on the Internet. This is logged for billing purposes and then the CID information is passed on to the system.

Comment Really simple. (Score 1) 110

Stop accepting any calls routed from unknown phone companies. It will stop 99% of them that are simply a freaking PC that is making VOIP calls via a scumbag VOIP service provider that will let them send whatever CID information they want.

Call coming into AT&T from a unknown and untrusted call routing? Refuse it.

Comment Re:who wants it? (Score 2) 396

But with bash you can just start typing text. No need to look up obscure command system and object names if they only thing you want to do is get a list of all files matching a pattern.

You must be one of those people who wonders why foreigners speak foreign languages when English is so much easier to learn! (Even our children can do it) Bash is not magically easier than PowerShell for someone who only uses it twice a year. In fact, I would say that PowerShell is easier because it has a lot of built-in aliases to make it familiar to *nix users.

Want to do a directory listing of all files matching a patter? Try ls *.txt. It will work in both bash and PowerShell. The arguments are different in PowerShell, but it's just a man ls to find out what they are (or just use the more convenient tab completion). Of course, those aliases are shortcuts to a verbose command naming scheme. I would think that for a very occasional user who might not remember the commands, it is far easier to use a system that has real descriptive names rather than the ultra-terse naming scheme used by *nix. Even if you can't remember the exact name in PowerShell, you can simply use a wildcard for the command name. Can't remember the command to export a CSV file? Type *csv* and keep pressing tab to cycle through the commands (or type man *csv* to see the entire list). If the occasional bash user had to export a CSV what would they do?

Also, PowerShell has a much more consistent argument naming scheme. The basic utilities on *nix have a diverse structure are arguments. For example, ls and find cover a similar subject, yet their arguments are worlds apart. You may be used to that, and so it seems familiar, but it is certainly not a simple case a sitting down and typing.

The difference is that Unix is oriented around commands and programs that take input and give output; whereas Windows is oriented around DLLs and frameworks that build on top of DLLs.

That is not an accurate assessment. PowerShell is all about commandlets and functions that take input and give output. The difference is that the input and output isn't just a stream of text, but objects. If you want to get the size of a file, you read it as a number; you don't have to convert the text in a particular position of a directory listing.

The pipeline is super-important in PowerShell. Objects, and lists of objects, are passed around and processed either sequentially or in a batch. The objects and pipeline are basically what gives PowerShell its power. To ignore that and talk about DLLs is just missing the entire point.

Comment Re:It's not what I call a scripting language. (Score 3, Informative) 396

Wow, that's elegant.

Actually, depending on what was being piped, it could be simplified to:

cat file.txt | where PropertyName -match "regex"

But where the elegance lies is that the similar code would work for other conditions, beyond what grep could do. If you wanted to find all the long lines in a file, you would say:

cat file.txt | where Length -gt 80

Of course, if you use the scriptblock version with the { } characters, then you can do complicated expressions

# Find long lines that start with the word using
cat file.txt | where { $_.Length -gt 80 -and $_ -match '^using" }

# Find large files
dir | where Length -gt 1mb

# Find large files that were written within the last week (not optimised)
dir | where { $_.Length -gt 1mb -and $_.LastWriteTime -gt (get-date).AddDays(-7) }

This so-called non-elegant grep replacement can be used anytime you want to filter something. It doesn't have to be the contents of files or files themselves. Here I download the homepage and find the link to the privacy statement:

$html = invoke-webrequest
$html.Links | where InnerText -eq 'Privacy'

Comment Re:Heu.. ???? (Score 2) 396

After 20 years of MS trying to kill the shell, they relented and decided the Windows platform needed one.

What on Earth gave you the impression that Microsoft had been trying to kill the shell?

For over 20 years they have made improvements to scripting from COMMAND.COM to CMD.EXE when we all moved to Windows NT. They added the Windows Scripting Host in 1999 with a large number of languages supported. Ten years ago they came out with PowerShell, which they have implemented as a central component so that some of the configuration programs are simply just a front-end to PowerShell (to teach people the scripting ways of controlling their server software).

They have also implemented the Server Core installation option of Windows Server, and the user interface is just a command prompt. No taskbar or explorer shell. None of these things are Microsoft trying to kill the shell.

PowerShell is not a result of a "not invented here" syndrome. If they had just made a copy of bash, then it would not done nearly as much as what PowerShell achieves. Microsoft didn't just try to be different, they tried to come up with something better.

Comment Re:Heu.. ???? (Score 1) 396

What I particularly dislike is how it automatically filters output, and you have to use arguments or other applets to give you fuller output. It just strikes me as being the exact opposite of how any particular command or script should work.

No, it is not the opposite. It's giving the information that is the most usable and easily read by a human. Even *nix utilities do this. Hell, type "ls" and you don't get the file sizes and dates; you have to add -l to get those details.

And objects, big fucking deal. I've been using Bourne variants for a quarter of a century and never thought "Boy, I wish I had classes".

That just shows that you are stuck in the mindset of manipulating text outputs of commands to find the information you need. It certainly shows a lack of imagination that there could be anything better. What it doesn't show is that there is anything wrong with the concept of PowerShell simply because you don't get it.

When you start writing scripts that make web requests that you can read the value you want without having to do clunky regular expressions, then directly updating specific cells in a spreadsheet (including with formatting) then you realise just how much easier this is with an object-based system. Or how about writing your own software as a .NET library so that the same code can be used for manual viewing in a .NET application or with powerful scripting with PowerShell with no additional effort.

Comment Re:Heu.. ???? (Score 1) 396

Embrace, extend and extinguish ???

Seriously, that is utterly moronic! Why do they need to embrace their own product? Surely they could easily extend PowerShell without making it open source - BECAUSE THEY ALREADY HAVE THE SOURCE! And why would they extinguish one of the core part of Windows? And how could they if they made it open source?

You simply saw the name Microsoft and just jumped to the old, out-of-date triple-E meme that has absolutely no relevance to the topic. Pathetic.

Slashdot Top Deals

Real Users never know what they want, but they always know when your program doesn't deliver it.