The issue with that argument is Windows keeps depreciating existing functionality so old experience is worthless fairly quickly. Nobody has decades of expertise with Windows 11, at this point with how little Windows 3.11 experience still applies. Remember .ini files? Yea how relevant is that today? How about using a DOS prompt recently?
Also: it's hardly improved significantly over the past 25 years! It's as rubbish as ever. If attempting to make the argument that Windows is changing stuff all the time, the command prompt really is the oddest thing to point at.
systems evolve. systemd is nearly fifteen years old and is not hard to use, and it is better than the myriad systems it replaced. that's why it won
this is very much not the same thing especially since you can still find non systemd distros but really, systemd is neither a new nor abrupt nor unilateral change
Linux is not "doing the same thing" except inasmuch that everything that doesn't die changes over time
Remember .ini files? Yea how relevant is that today?
AFAIK there's nothing stopping you from writing software that pulls config info from an ini file. Has something changed?
Edit: I think I've edited ini files to configure video games somewhat recently.
How about using a DOS prompt recently?
I host my command prompt inside a 3rd party program, but I still use the Windows command prompt all the time. I think that's pretty normal for "power users" who haven't moved on to PowerShell (I use PS when I have to, but it's not my go-to).
> writing software that pulls config info from an ini file.
You can write a Linux program that pulls from an INI file or a 3rd party DOS program on MacOS, the question is how this stuff is relevant to being a power Windows user.
You can write a Linux program that pulls from an INI file
What's the API for that look like? In Win32 it's GetPrivateProfileString.
the question is how this stuff is relevant to being a power Windows user.
I gave you an example. I guess you're not aware that many desktop applications continue to support ini files, even if it's not the first line of configuration anymore.
I am well aware of INI files being used by applications on several operating systems. DotNet Core may not be the most popular platform but it’s blurred the lines here.
DOS has similarly been stripped from Windows but 3rd party DOS shells exist on many platforms. Honestly knowing Bash is more Windows specific at this point than DOS. https://learn.microsoft.com/en-us/windows/wsl/install
So again, none of your examples are Windows specific at this point.
DOS has similarly been stripped from Windows but 3rd party DOS shells exist on many platforms
Huh? DOS != Command line interpreter or shell. DOS per se hasn't existed for decades, but the command line (Command Prompt) lives on, using pretty much the same syntax.
Honestly knowing Bash is more Windows specific at this point than DOS.
Bash is more Windows-specific than "DOS"?! That makes no sense whatsoever.
I am well aware of INI files being used by applications on several operating systems.
What are you even talking about now? You started the whole ini discussion with "Remember .ini files? Yea how relevant is that today?" So it went from irrelevant to relevant across platforms?
On windows 11 using Microsoft only tools you can list every file in a directory using ls or dir. But Bash is by far a more powerful tool than command prompt making it far more relevant for a power user than some legacy syntax.
> So it went from irrelevant to relevant across platforms?
The point INI files and DOS come up but aren’t some Windows specific knowledge at this point.
