When downloading the exe launcher (not the MSI), common practice in the past was to simply place this on the desktop and run from there. Or leave somewhere like a "minecraft stuff" folder, and create a shortcut
Doing so with this new launcher results in:
A "tmp" folder being created, and eventually left empty.
A folder filled with what appears to be the launcher GUI elements
A folder containing an unnecessary Java environment.
This results in a mess on the desktop if run there. Or even possible data loss if existing files match the path the launcher uses.
The correct behaviour IMO would be:
Check for existing suitable JRE (64/32 bit, too old, etc).
Refuse to run if existing JRE is known insecure.
Use existing JRE if found.
Prompt user before downloading custom JRE.
Use normal Minecraft path for data storage.
Ignore the JRE bit if this is now a forced policy from Microsoft... But the folder spam is not acceptable.
Regarding the launcher creating files and folders in the same directory: As far as I know the old
.exelauncher did the same, see MCL-3343Edit: Currently a custom JRE can only be set when you enable "Advanced settings". Therefor suggesting to use a custom JRE when you start the launcher for the first time for all users is maybe not what the developers intend. But I can confirm that the launcher still downloads the JRE even if all profiles use a different one.