The first thing I am trying to do is install as many of the programs that I always like to have available as possible. I would appreciate any insights or guidance on these questions as I begin to work on this project.My goal is to create a single script that I can download and run on a fresh Windows build to set up the system as much as possible. Thus, far I have explored the idea of using both Go,Rust,C#,C++ and Make it more useful and efficient for Windows users? What are some additional features or capabilities that I shouldĬonsider incorporating into my native SDKMAN tool for Windows to Manager with shims for Windows, and how can I avoid them whileīuilding a native SDKMAN tool for Windows? What are some common challenges and pitfalls in building a package Integration with the Windows environment? How can I create and manage shims effectively in my package manager,īased on the experience of Scoop and Chocolatey, to ensure seamless Package manager for Windows, and how can they be optimized for

What are the advantages and disadvantages of using shims in a Windows, and how can they be adapted to create a Windows-native What are the key components of a package manager with shims for I want to enable Windows users to access the same features and benefits that Linux and Mac users have been enjoying with SDKMAN for years, while also leveraging the advantages of shims for seamless integration with the Windows environment. My ultimate goal is to make it easier for Windows users to manage their Java and other software development kits using SDKMAN. To get started, I would like to learn from the experience of existing package managers like Scoop and Chocolatey, and understand the pros, cons, and areas for improvement in their approach.

I am embarking on a project to create a Windows-native version of SDKMAN that utilizes shims to manage software installations and updates.

Chocolatey powershell