Orc-tal; trolling from the nerdy jokes thread
-
@Atazhaia said in The nerdy jokes thread (bonus original title mode!):
FTFY
Bugger; hadn't finished my coffee.
Corrected, ta.
-
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra Only when they can't be represented any other way. Most of the time, they're just something like NT AUTHORITY\TrustedInstaller or DESKTOP-WHRGRBL\Adam. They're stored as magic numbers but only a retarded system would make you interact with them as magic numbers.
Ah, good, so we've established that Linux isn't retarded then.
-
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Blakey says it all the time.
-
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
Deprecated since 2008.
But you don't provide equivalent operations to compare against with things that are current. Nice. Arguing with you is like arguing with a version of blakeyrat that's both stupid and wrong.
-
What is this fuckery in my thread, don't make me
chmod o-w
this whole thing!Besides, POSIX permissions are clearly superior because you can
chmod 007
a file.
Filed under: Licence to be killed
-
This is supposed to be the nerdy jokes thread, not the nerdy slapfight thread.
-
@Onyx said in The nerdy jokes thread (bonus original title mode!):
Besides, POSIX permissions are clearly superior because you can
chmod 007
a file.Oi! That's on topic!
-
@Onyx said in The nerdy jokes thread (bonus original title mode!):
Besides, POSIX permissions are clearly superior because you can
chmod 007
a file.
Filed under: Licence to be killed
If you chmod anything to 007 you should be.
-
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
I can't imagine it would be difficult to map attrib or type to a PowerShell command with full compatibility.
Dunno about
attrib
buttype
is a valid alias (AFAIK it's preset by default) for the equivalent Powershell command.
-
@PleegWat said in The nerdy jokes thread (bonus original title mode!):
@Onyx said in The nerdy jokes thread (bonus original title mode!):
Besides, POSIX permissions are clearly superior because you can
chmod 007
a file.
Filed under: Licence to be killed
If you chmod anything to 007 you should be.
Well, I'm the person who once ran
chmod -R 666 /
... And only realized the mistake oncechmod
already gotchmod
ed as well...For the better probably, reinstall was a faster option either way
-
@Onyx Higher scripting languages like
perl
orpython
have chmod as a builtin and are in/usr/bin/
, so they might still work. Could still be faster to reinstall depending on what the mess looked like even before then.
-
Stop ruining the jokes thread.
-
@loopback0 said in The nerdy jokes thread (bonus original title mode!):
Stop ruining the jokes thread.
You expect something not to get ruined here?
Thread over, you just posted the equivalent of posting "Chuck Norris" in a "who would win in a fight?" thread.
-
@dkf said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
Deprecated since 2008.
But you don't provide equivalent operations to compare against with things that are current. Nice. Arguing with you is like arguing with a version of blakeyrat that's both stupid and wrong.
But is it a version that's a stupid idiot regard moron?
-
@Onyx said in The nerdy jokes thread (bonus original title mode!):
What is this fuckery in my thread
K tried to stop it, really, I did...
-
-
@boomzilla
We didn't need to know about the warthog's fetish for being work-raped.
-
@izzion that was just sympathy sweat. I certainly didn't fork this thread.
-
@PJH said in Orc-tal; trolling from the nerdy jokes thread:
Even the Linux CLI doesn't make you interact with them as magic numbers.
chmod ugo+rwX ...
And far more convenient, because you don’t have to explicitly set permissions you don’t want to change if, say, you want to write-protect a file.
(Also, I can never remember which values correspond to r, w, and x so it’s far quicker to just specify them by letter.)
-
@Gurth said in Orc-tal; trolling from the nerdy jokes thread:
Also, I can never remember which values correspond to r, w, and x
If you can remember them in that order, they're in descending numerical order (4,2,1)
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@dkf said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
That's highly abbreviated because it's trying to show everything about directories at once. ACLs themselves are represented in a much more high-level way when specifically editing them, rather than strange letters.
But the format for describing them is just as mysterious as that you get with the Linux command line. An example from earlier up the thread had
(OI)(CI)(IO)F
as description, and that's definitely not obvious at first glance. It might be clear to you because of what you have learned, but that's definitely not clearer than-rw-r--r--
; neither is actually intuitive, and both are interfaces intended for people with some expertise (i.e., so they can actually read the abbreviated forms). Security descriptors are pretty opaque to most users.Also, what does
(OI)(CI)(IO)F
actually mean? I can see from the example that theF
is sometimes replaced with(special access:)
with a longer description beneath (nor do I understand the significance of the terms in the special access expansion; I guess I could look those up though, as they look like they'd be googleable), but that doesn't tell me what those standard forms do, andIO
totally doesn't have a bazillion other meanings. I'm curious…Deprecated since 2008.
Obviously not.
Obviously.
-
@dkf said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
Deprecated since 2008.
But you don't provide equivalent operations to compare against with things that are current. Nice. Arguing with you is like arguing with a version of blakeyrat that's both stupid and wrong.
Actually, I did. You're supposed to use Get-Acl and Set-Acl when you use PowerShell.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@dkf said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
That's highly abbreviated because it's trying to show everything about directories at once. ACLs themselves are represented in a much more high-level way when specifically editing them, rather than strange letters.
But the format for describing them is just as mysterious as that you get with the Linux command line. An example from earlier up the thread had
(OI)(CI)(IO)F
as description, and that's definitely not obvious at first glance. It might be clear to you because of what you have learned, but that's definitely not clearer than-rw-r--r--
; neither is actually intuitive, and both are interfaces intended for people with some expertise (i.e., so they can actually read the abbreviated forms). Security descriptors are pretty opaque to most users.Also, what does
(OI)(CI)(IO)F
actually mean? I can see from the example that theF
is sometimes replaced with(special access:)
with a longer description beneath (nor do I understand the significance of the terms in the special access expansion; I guess I could look those up though, as they look like they'd be googleable), but that doesn't tell me what those standard forms do, andIO
totally doesn't have a bazillion other meanings. I'm curious…Deprecated since 2008.
Obviously not.
Obviously.
What?
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@dkf said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
That's highly abbreviated because it's trying to show everything about directories at once. ACLs themselves are represented in a much more high-level way when specifically editing them, rather than strange letters.
But the format for describing them is just as mysterious as that you get with the Linux command line. An example from earlier up the thread had
(OI)(CI)(IO)F
as description, and that's definitely not obvious at first glance. It might be clear to you because of what you have learned, but that's definitely not clearer than-rw-r--r--
; neither is actually intuitive, and both are interfaces intended for people with some expertise (i.e., so they can actually read the abbreviated forms). Security descriptors are pretty opaque to most users.Also, what does
(OI)(CI)(IO)F
actually mean? I can see from the example that theF
is sometimes replaced with(special access:)
with a longer description beneath (nor do I understand the significance of the terms in the special access expansion; I guess I could look those up though, as they look like they'd be googleable), but that doesn't tell me what those standard forms do, andIO
totally doesn't have a bazillion other meanings. I'm curious…Deprecated since 2008.
Obviously not.
Obviously.
What?
Exactly. How's it obvious? I cited a high ranking Microsofter as saying so. What's your source for saying it's not?
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
I cited a high ranking Microsofter as saying so.
False.
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
What's your source for saying it's not?
So you're asking me to prove the absence of something. Got it.
-
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
I'm a Social VR Game architect! And I declare all other Social VR Games deprecated!
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
I'm a Social VR Game architect! And I declare all other Social VR Games deprecated!
You're kidding me, right?
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
I'm a Social VR Game architect! And I declare all other Social VR Games deprecated!
You're kidding me, right?
You still maintain that so long as you close your eyes you're not bound to copyright law, right?
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
I'm a Social VR Game architect! And I declare all other Social VR Games deprecated!
You're kidding me, right?
You still maintain that so long as you close your eyes you're not bound to copyright law, right?
No. I haven't ever said that once.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra said in The nerdy jokes thread (bonus original title mode!):
@pie_flavor said in The nerdy jokes thread (bonus original title mode!):
@Tsaukpaetra CMD's output is about as meaningful to me as VB6's. PowerShell is the intended way of interfacing with Windows from the command line.
[Citation Needed]
Was the fact that every Win10-specific action is only available in PowerShell and that the Win+X menu changed from CMD to PowerShell and that the shift right click menu has Open PowerShell Window Here instead of Open Command Prompt here in it not clue enough?
No.
Also:
Yes, I know that's a setting that you changed away from the default.
The command I used has been available since Vista (when it superceded
cacls.exe
from Windows XP (which also still works, natch):And the intended way to do this is Get-Acl and Set-Acl.
So, again, [Citation needed]
Here, here's another one, by the PowerShell Chief Architect.
https://www.youtube.com/watch?v=us4HTxtjfa8&t=1230
Apparently it's been deprecated since 2008.Just going to repeat that qualification. PowerShell Chief Architect.
I'm a Social VR Game architect! And I declare all other Social VR Games deprecated!
You're kidding me, right?
You still maintain that so long as you close your eyes you're not bound to copyright law, right?
No. I haven't ever said that once.
Fine then, that if a product that nominally would contain a EULA but which was obtained altered such that the EULA was not presented (or was otherwise ignored, a la closing your eyes) necessarily means that breaking the EULA holds no consequences and is perfectly legal.
-
@Tsaukpaetra No, breaking a EULA is always illegal. But it's not breaking it if you never agreed to it in the first place. No court has ever found that you can be bound by an implicit agreement that you are not presented with.
Can we get back to the part where you ignored logic directly? Because unless you meant me to interpret this as 'you ignored logic in this other thread therefore I get to ignore logic here', which I don't think you do, you directly ignored logic there. The chief architect of PowerShell cannot say that Bash is deprecated, because he has nothing to do with Bash and they are run by completely separate entities. But the chief architect of PowerShell can say that CMD is deprecated, because he is employed by the same company that makes CMD.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Can we get back to the part where you ignored logic directly?
Why?
Because unless you meant me to interpret this as 'you ignored logic in this other thread therefore I get to ignore logic here', which I don't think you do, you directly ignored logic there.
What?
But the chief architect of PowerShell can say that CMD is deprecated, because he is employed by the same company that makes CMD.
Let me ask you this then: Can the Director of Lunar Aviation (in a company that specializes in aircraft) claim that Earth-based airplanes are deprecated, when their flagship product trundles around in the plebian atmosphere of Earth?
Put another way: Can the Head Honcho of one department claim a product of another department (in the same company) is deprecated?
And, are those claims necessarily as legitimate as one who is actually in the department in question?
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Can we get back to the part where you ignored logic directly?
Why?
Because unless you meant me to interpret this as 'you ignored logic in this other thread therefore I get to ignore logic here', which I don't think you do, you directly ignored logic there.
What?
But the chief architect of PowerShell can say that CMD is deprecated, because he is employed by the same company that makes CMD.
Let me ask you this then: Can the Director of Lunar Aviation (in a company that specializes in aircraft) claim that Earth-based airplanes are deprecated, when their flagship product trundles around in the plebian atmosphere of Earth?
Different thing. That's not a single product, that's a class of products, and they're not meant to fit the same goal. If they make two airplanes, then the head honcho of the department of one of them can claim that the other one is deprecated, yes.
Put another way: Can the Head Honcho of one department claim a product of another department (in the same company) is deprecated?
Yes.
And, are those claims necessarily as legitimate as one who is actually in the department in question?
Feel free to find me a video of a CMD team head honcho saying CMD is still the recommended product. But I don't think there even is a CMD team anymore.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Feel free to find me a video of a CMD team head honcho saying CMD is still the recommended product. But I don't think there even is a CMD team anymore.
Feel free to find me a video (or docs! There's still docs about everything you can do in Command Prompt!) saying it's no longer supported (aka deprecated) from the CMD team.
Because, usually, there's a big ol "Hey guys! Heads up! Y'all can be using that no more, this is the last version and it is deprecated as of X. Check out its replacement, Y, which does everything Z did, but better!" announcement.
See all the news, notifications, and documentation artifacts that now state Windows XP is deprecated for examples.
-
Again, I'm going to refuse to prove the absence of something.
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Feel free to find me a video of a CMD team head honcho saying CMD is still the recommended product. But I don't think there even is a CMD team anymore.
Feel free to find me a video (or docs! There's still docs about everything you can do in Command Prompt!) saying it's no longer supported (aka deprecated) from the CMD team.
There isn't a CMD team.
Because, usually, there's a big ol "Hey guys! Heads up! Y'all can be using that no more, this is the last version and it is deprecated as of X. Check out its replacement, Y, which does everything Z did, but better!" announcement.
I linked a video mentioning that it is deprecated as of 2008, talking about how PowerShell does everything CMD did but better.
See all the news, notifications, and documentation artifacts that now state Windows XP is deprecated for examples.
Different. XP hit the end of support. CMD hasn't done that yet.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
There isn't a CMD team.
You sure? Cause there were changes in the last update (1809).
-
@dcon really? And yeah, they don't have a dedicated team because it's very simple and it's not a dedicated product.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Feel free to find me a video of a CMD team head honcho saying CMD is still the recommended product. But I don't think there even is a CMD team anymore.
Feel free to find me a video (or docs! There's still docs about everything you can do in Command Prompt!) saying it's no longer supported (aka deprecated) from the CMD team.
There isn't a CMD team.
So why do you expect me "to find me a video of a CMD team head honcho saying CMD is still the recommended product." ?
And if this is true, why have they not removed this (obviously) unsupported product from their operating system? And you accuse me of ignoring logic.Because, usually, there's a big ol "Hey guys! Heads up! Y'all can be using that no more, this is the last version and it is deprecated as of X. Check out its replacement, Y, which does everything Z did, but better!" announcement.
I linked a video mentioning that it is deprecated as of 2008, talking about how PowerShell does everything CMD did but better.
Which is why
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
Additionally, if they really intended PowerShell the be the de-facto shell for Windows, why does cmd.exe not simply link to it?
Apparently, doing "everything CMD did but better." doesn't mean "it's a replacement for". Who knew?
See all the news, notifications, and documentation artifacts that now state Windows XP is deprecated for examples.
Different. XP hit the end of support. CMD hasn't done that yet.
And yet, there were deprecation warnings years before end of support. So, where are they? Can you show me other than some random talk from a dude trying to drum up hype for a replacement-but-not-really product that (so far as you've failed to provide anything more substantial) has claimed Command Prompt is deprecated?
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@dcon really? And yeah, they don't have a dedicated team because it's very simple and it's not a dedicated product.
Apparently Microsoft spends effort on deprecated things that they haven't marked as deprecated.
Because that's what deprecation means nowadays.
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Feel free to find me a video of a CMD team head honcho saying CMD is still the recommended product. But I don't think there even is a CMD team anymore.
Feel free to find me a video (or docs! There's still docs about everything you can do in Command Prompt!) saying it's no longer supported (aka deprecated) from the CMD team.
There isn't a CMD team.
So why do you expect me "to find me a video of a CMD team head honcho saying CMD is still the recommended product." ?
Because that was your hypothetical condition. You said,
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
And, are those claims necessarily as legitimate as one who is actually in the department in question?
There is no claim from someone who is actually in the department in question that I know of. Unless you can procure one, then this question is entirely pointless. If there was a claim from someone in the department in question, that'd be slightly more credible than someone in the PS department, but in its absence, the PS chief architect is pretty damn credible.
And if this is true, why have they not removed this (obviously) unsupported product from their operating system? And you accuse me of ignoring logic.
Because Windows is committed to backwards compatibility at all costs. That's you ignoring logic, yeah. Why the hell would they remove literally the most executed program in the system? Deprecated means 'we have something better', not 'we're deleting this tomorrow'.
Because, usually, there's a big ol "Hey guys! Heads up! Y'all can be using that no more, this is the last version and it is deprecated as of X. Check out its replacement, Y, which does everything Z did, but better!" announcement.
I linked a video mentioning that it is deprecated as of 2008, talking about how PowerShell does everything CMD did but better.
Which is why
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
Additionally, if they really intended PowerShell the be the de-facto shell for Windows, why does cmd.exe not simply link to it?
Apparently, doing "everything CMD did but better." doesn't mean "it's a replacement for". Who knew?
It is a replacement for CMD. It is not a drop-in replacement for CMD. There's different commands and different arguments. Are you listening to yourself?
See all the news, notifications, and documentation artifacts that now state Windows XP is deprecated for examples.
Different. XP hit the end of support. CMD hasn't done that yet.
And yet, there were deprecation warnings years before end of support. So, where are they? Can you show me other than some random talk from a dude trying to drum up hype for a replacement-but-not-really product that (so far as you've failed to provide anything more substantial) has claimed Command Prompt is deprecated?
Yes, 'a dude'. Not 'chief architect of one of the two relevant Microsoft products', just 'a dude'. This is how I can tell you're not arguing in good faith.
Meanwhile, all the notifications were about the support ending. And now the support has ended. CMD's support is nowhere near ending.
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@dcon really? And yeah, they don't have a dedicated team because it's very simple and it's not a dedicated product.
Apparently Microsoft spends effort on deprecated things that they haven't marked as deprecated.
Because that's what deprecation means nowadays.
Deprecated means that something's obsolete and has a better replacement. It doesn't mean you can't add features to it, for people that are still stuck using it.
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Deprecated means 'we have something better', not 'we're deleting this tomorrow'.
No, it means it is no longer supported (which does imply your first point). And (at least in software) implies that it will be removed in the future. If features are being added, it's not deprecated.
-
@dcon I wasn't sure whether I had that right, so I checked:
https://i.imgur.com/jFyl4ZH.png
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@dcon really? And yeah, they don't have a dedicated team because it's very simple and it's not a dedicated product.
Apparently Microsoft spends effort on deprecated things that they haven't marked as deprecated.
Because that's what deprecation means nowadays.
Deprecated means that something's obsolete and has a better replacement. It doesn't mean you can't add features to it, for people that are still stuck using it.
Because adding features to something you're actively trying to move people away from is just what you do nowadays.
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
There is no claim from someone who is actually in the department in question that I know of. Unless you can procure one, then this question is entirely pointless.
No, that's precisely the point. You can't do this one simple thing, and that's the point.
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
It is a replacement for CMD. It is not a drop-in replacement for CMD. There's different commands and different arguments.
And as I asked before (and you candidly ignored), what's to stop them from making it so? Others have pointed out that there are already aliases for many of the common commands, so what's left?
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
Are you listening to yourself?
Are you?
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
This is how I can tell you're not arguing in good faith.
Why would you presume I'm arguing in good faith on a forum specifically for complaining about things? Are you new here? Are you not a regular denizen of the Trolleybus Garage?
-
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@dcon I wasn't sure whether I had that right, so I checked:
https://i.imgur.com/jFyl4ZH.pngOne easy way to get people to avoid a product is to stop updating it.
Clearly they're sending mixed signals.
-
@pie_flavor Here. Have a wikipedia definition.
-
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@Tsaukpaetra said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
@dcon really? And yeah, they don't have a dedicated team because it's very simple and it's not a dedicated product.
Apparently Microsoft spends effort on deprecated things that they haven't marked as deprecated.
Because that's what deprecation means nowadays.
Deprecated means that something's obsolete and has a better replacement. It doesn't mean you can't add features to it, for people that are still stuck using it.
Because adding features to something you're actively trying to move people away from is just what you do nowadays.
For the people who are stuck using it, yes.
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
There is no claim from someone who is actually in the department in question that I know of. Unless you can procure one, then this question is entirely pointless.
No, that's precisely the point. You can't do this one simple thing, and that's the point.
What? You gave me a hypothetical, dependent on you having some statement, and you don't have that statement. How's that meaningful?
@pie_flavor said in Orc-tal; trolling from the nerdy jokes thread:
It is a replacement for CMD. It is not a drop-in replacement for CMD. There's different commands and different arguments.
And as I asked before (and you candidly ignored), what's to stop them from making it so? Others have pointed out that there are already aliases for many of the common commands, so what's left?
Changing everything else about it? While we're at it, why not make C code work in Rust?
Also, I see you neglected to respond to the last point. Should I assume that you've conceded that you're wrong about deprecation warnings?
-
@dcon said in Orc-tal; trolling from the nerdy jokes thread:
@pie_flavor Here. Have a wikipedia definition.
The feature has been replaced by a more powerful alternative feature. For instance, the Linux kernel contains two modules to communicate with Windows networks: smbfs and cifs. The latter provides better security, supports more protocol features, and integrates better with the rest of the kernel. Since the inclusion of cifs, smbfs has been deprecated.
Sounds about right.