does windows terminal have environment variables like $PATH and shit?

yes

https://msdn.microsoft.com/en-us/library/windows/desktop/ms682653(v=vs.85).aspx

>>59132104
run cmd
type set

>yes

>>59132142
>>59132130
>>59132128
they stole this from unix

>>59132156
That's such a pointless statement...

>>59132156
DOS itself was the bastard child of CP/M and Unix. Microsoft wanted / for pathsep and - for switches, too. Blame IBM for the \ pathsep and/ switches. PowerShell has a bunch of Unix aliases like cp, rm, mv, and ls.

>>59132104
obviously moron.

programs that depend on external software must be able to source them relative of their actual install location.

there is even a way to set your default path variable in wndows.
I don't remember the exact process, but it is more convoluted than setting your /etc/profile or local .*rc

>>59132104
Yes but batch script language is autistic. You dereference variables using %VAR% rather than $VAR, everything is a string by default (no need for quotation marks) and you can only do arithmetic to variables assigned using SET /A. Also you don't have functions, best you can do is GOTO storing arguments and results in global variables.

>>59132156
>>59132405
Powershell is basically C# plus bash.

>>59132446
DOS and Windows do have some Unix ideas, like "device files" and redirection, but it's basically tacked on as an afterthought rather than being an integral part of the system like Unix. And the whole backslash retardation is because the original version of DOS didn't have directories, just disks, and they decided to use the forward slash for switches (not sure why they didn't just use a dash like Unix), which meant when they added directories they had to use something else as separator.

>>59132901
I unironically like powershell better than bash. For sysadmin it is better. I really wish bash had some OO equivalent because returning objects is awesome and allows you to focus on tasks instead of text parsing.