Skip to main content
Super User

Return to Answer

replaced http://superuser.com/ with https://superuser.com/
Source Link
Community Bot
Community Bot
  • 1

My perspective:

Questions why something wasn't implemented in a standardwasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interfaceloopback interface I don't personally feel it's a good question honestly. As for the reason questions exists on Stack Overflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows featureWindows feature doesn't do something, there isn't a way to know the specific reason. Besides, if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are Windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is work to be done (to improve either on the question or the answer).

My perspective:

Questions why something wasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interface I don't personally feel it's a good question honestly. As for the reason questions exists on Stack Overflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something, there isn't a way to know the specific reason. Besides, if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are Windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is work to be done (to improve either on the question or the answer).

My perspective:

Questions why something wasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interface I don't personally feel it's a good question honestly. As for the reason questions exists on Stack Overflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something, there isn't a way to know the specific reason. Besides, if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are Windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is work to be done (to improve either on the question or the answer).

Copy edited. Removed meta information. (its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-its-and-it's>.) Used the official names of Stack Overflow - see http://stackoverflow.com/legal/trademark-guidance (the last section).
Source Link
Peter Mortensen
Peter Mortensen
  • 12.3k
  • 16
  • 11

So I decided to post myMy perspective.:

Questions why something wasn't implemented in a standardwasn't implemented in a standard is easier to answer. AsAs for the other question about why Microsoft didn't implement a loopback interface I don't personally feel itsit's a good question honestly. AsAs for the reason questions exists on StackoverflowStack Overflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something. There, there isn't a way to know the specific reason. BesidesBesides, if that question were to be answered today, it would be different, considering that feature will be in Windows 10Windows 10. TheThe linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are windowsWindows command line programs that do support that shortcut. TheThe answer to a question should be based on fact. AA question normally is in trouble if more than two people are posting an answer which presents their opinion. AnAn answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is workedwork to be done ( toto improve either on the question or the answer  ).

So I decided to post my perspective.

Questions why something wasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interface I don't personally feel its a good question honestly. As for the reason questions exists on Stackoverflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something. There isn't a way to know the specific reason. Besides if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is worked to be done ( to improve either on the question or the answer  ).

My perspective:

Questions why something wasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interface I don't personally feel it's a good question honestly. As for the reason questions exists on Stack Overflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something, there isn't a way to know the specific reason. Besides, if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are Windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is work to be done (to improve either on the question or the answer).

Source Link
Ramhound
Ramhound
  • 43.6k
  • 2
  • 21
  • 29

So I decided to post my perspective.

Questions why something wasn't implemented in a standard is easier to answer. As for the other question about why Microsoft didn't implement a loopback interface I don't personally feel its a good question honestly. As for the reason questions exists on Stackoverflow, I cannot answer, since I am not involved as much in that community for a variety of reasons.

As for the reason a Windows feature doesn't do something. There isn't a way to know the specific reason. Besides if that question were to be answered today, it would be different, considering that feature will be in Windows 10. The linked question has very little to do with PowerShell, it was erroneously, connected to PowerShell by the commenters.

There are windows command line programs that do support that shortcut. The answer to a question should be based on fact. A question normally is in trouble if more than two people are posting an answer which presents their opinion. An answer can involve some educated guessing on what the solution might be, but if that solution isn't based on fact, then there is worked to be done ( to improve either on the question or the answer ).