3 ms·
PowerShell also needs all the other dll's located next to the executable so it's way more than 440k. Granted I agree that this isn't a space they really care ab
by jborean93 2y ago
PowerShell also needs all the other dll's located next to the executable so it's way more than 440k. Granted I agree that this isn't a space they really care about and the problem is more due to the dependency on .NET itself.
- dekhn 2y agoWell, I assumed the 100K dash shell also was dynamically linked (presumably to libc and the linker loader). But yes, you're right, I wasn't including all the DLLs and all the various modules/scripts you can invoke. from my inspection, it looks like DLLs that are probably already loaded just by booting a system.
- jborean93 2y agoIt's more for pwsh (7+) as that bundles it's own copy of the .NET runtime. The powershell.exe (5.1) is the version included in Windows and uses a shared copy of the .NET Framework included in the GAC. When looking at the size of modern PowerShell (7+) you do need to take into consideration the size of the .NET runtime which is quite sizeable. Personally it's not a problem for me and while I don't agree it's a fatal flaw it's certainly a downside compared to other shells.