• 1 Post
  • 54 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle

  • Which is fine when people do not reject the answers that are different from what they were expecting. Learning that the problem you have is a reason that noone does this, is a valid thing to learn.

    It’s usually when I see people moving the goal posts on replies, or complaining that they didn’t answer the exact question that i see as frustrating. Or “I don’t want to do that” with no more info.

    But if you are aware of other solutions, you should state that in the question and give your reasons. It’s a waste of time if you know someone might suggest what you have dismissed already.

    The html question is a classic for this, they want to find non self closed tags. Why? Why can’t they use a parser? What are they doing with this info? All questions that would give you a good idea on how the problem can be solved. Playing with regex would be a valid answer to that, but is not stated. Unfortunately I find so’s format discourages extra interrogation.

    The answer is not an attack on the person, but a frustration at the people before that ignored previous answers to use a parser.
















  • Since you added a question mark, commands is the correct general term. However there are two types that can be a command. Functions: which are written in pure powershell and cmdlets: which are commands provided by dotnet classes. (Also exes and a bunch of other stuff common to other shells can be a command, but that’s not important.)

    The reason they have different names is early on functions didn’t support some of the features available to cmdlets, such as pipeline input. There was later a way to add this support to functions.

    In practice call them any of the 3 and people will know that you mean.