Neither does it mean it is guaranteed to be a part of the stigmatization. But your post implied that it is.
Absolutely not. It only adds the
impression that it is. "The trick, William Potter, is
not minding that it hurts."
And one of the main reasons sites like this work is because you have a diverse set of options presented whenever someone asks for help. Not only for the OP, but for anyone reading the thread at a later date because they have the same issue, question, or request. And if a person succumbs to this because of a so-called lack of this awareness that you speak of, then that would mean that no one, ever, would be able to offer any advice or opinion - because every person's opinion on everything would then be open to being regarded as the basis of some sort of stigmatization.
Aside from just jokes, you don't see me post anything that could even remotely suggest that I believe using the built-in tools is almost always a poor choice. Either you have very poor reading comprehension skills or else you are trying to stigmatize me by claiming that you see me post it anyway. The reality is that anyone who has been reading my posts already knows that I am not against using the built-in tools, as I use them for a lot of things.
So, you're basically saying that
@z3r010 should shut all his forums down because a single subset of people here (everyone offering opinions for others asking for advice or support) is, in some way, causing some sort of imagined stigmatization.
In your own imagination, yes, that could certainly be it.
It would be just as readily caused by someone coming into this thread, or any one like it, and saying
Nah. As you already know, you don't necessarily
have to open Windows Terminal for that, but especially on slower machines it can take a short moment before PowerShell starts and runs the command or script so, there can be a noticeable delay that easily contributes to why using PowerShell isn't always the best answer, even though it very often can be. Where feasible, I tend to often avoid this delay by using other built-in tools such as, e.g., the command prompt or a batchfile, Windows Scripting Host, and the C# compiler (csc.exe) that is part of the .NET Framework. The latter is installed on Windows 11 already by default.
There have been more than a few posts like this about using internal / built-in / native tools when they were suggested. But these don't also cause this so-called stigmatization?
Of course not. There is a big difference between using the built-in tools and being vocal about refusing to use 3rd party tools for anything besides small exceptions.
Because, if they do, you've basically given John a reason why the forums should no longer offer advice, and particularly any individual's opinionated advice, at any given time or in any given thread here.
See above. Also, I like turtles.
I never once mention any sort of guarantee of availability. I instead mention that the 3rd party tools may not be available. And Windows own tools breaking are not all of the service requests nor software advice given in this forum - or in any forum, really. So, I have no idea where you're trying to take this. But this wonderful quotation does go right back to your point of
Similarly, the built-in tools may not be available. So, it is a strawman argument, as this obviously cuts both ways and therefore doesn't add any logical reason why anyone would want to, with only very few exceptions, avoid 3rd party tools.
You're obviously over thinking what I've written there.
Not really. The part you quoted was just to clarify my response. It's human psychology 101. Nothing more, nothing less.
How do you compare the two if you don't use the native tools? How do you use the native tools if you don't learn how to use them?
See above. Using 3rd party tools does not in any way
prevent me from using the native tools, and, I never claimed that I don't use the native tools. I
do use the native tools, and use them for a lot of things actually. Sometimes they eliminate the need for a 3rd party tool. Sometimes they do not. There can be pros and cons. To be able to learn what are the pros and cons, I use
both 3rd party tools
and native tools. Or at the very minimum I investigate them both. My only real preference is knowing the important facts (if they affect my workflow and/or could potentially affect other people's workflow) before I pick my choice, and I also like to share this knowledge. (Even, if I'm not going to make many friends by sharing it, as people can still always choose to make friends on asocial media if that's their thing.)
You're taking this entirely too far, dude. Sorry, but I call total BS on your idea of stigmatization. Anyone reading these posts in this and all the similar threads like this is allowed to make their own choice. The only stigma here is that some people don't like to hear alternatives that don't fit their perception of what they want to use.
It isn't my idea of stigmatization. Stigmatization is the action of describing or regarding someone or something as worthy of disgrace or great disapproval so, do you mean to tell me that being vocal about relentlessly avoiding 3rd party tools is not adding the clear impression of great disapproval? lol...
The real stigmatization is your own reaction to their advice. And I'm not bothering with the rest of this because, frankly, you're over blowing the idea from nothing into something - or, rather, making a mountain out of a molehill.
So, here's my little piece of advice. Look up the definition of stigmatization, and, when you do, be sure to read the definition for what the definition truly is. Have a nice day!