Docker VS Scoop

I'm not touching anything Docker anymore.

Here's the scenario: you're the unfortunate soul who received the first M1 as a new employee, and nothing Docker-related works. Cue multi-arch builds; what a rotten mess. I spent more than a week figuring out the careful orchestration that any build involving `docker manifest` needs. If you aren't within the very fine line that buildx assumes, good luck pal. How long has `docker manifest` been "experimental?" It's abandonware.

Then I decided it would be smart to point out that we don't sign our images, and so I had to figure out how to combine the `docker manifest` mess with `docker trust`, another piece of abandonware. Eventually I figured out that the way to do it was with notary[1], another (poorly documented) piece of abandonware. The new shiny thing is notation[2], which does exactly the same thing, but is nowhere near complete.

At least Google clearly signals that they are killing something, Docker just lets projects go quiet.

How long before this project lands up like the rest of them? Coincidentally, we were talking about decoupling our CI from proprietary CI, seeing this was a rollercoaster of emotions.

[1]: https://github.com/notaryproject/notary

Scoop is a command-line installer for Windows, aimed at making it easier for users to manage software installations and maintain a clean system. It's designed with developers and power users in mind but can be beneficial for any Windows user looking for an efficient way to manage software. Basically it makes our life easier when it comes to software installation of any sort. Scoop support installation for large number of software. Check it out here Scoop.

Use a package manager! Assuming Windows (since it's the odd one out), get yourself some scoop then just scoop install openjdk. No need to navigate to a website, download bundleware, click next-next-next and accidentally install a virus like some caveman from 1997. This has been a solved problem since ancient times!

Should be easy enough, I installed neovim on my windows machine with scoop (you can even get nightly if you want), it's basically a one line install. You can also do a manual install if you want, but you don't have to. It took a little fiddling for me because I wanted to install scoop as well as all applications onto my D drive rather than my C drive, but nothing too crazy. I never got NvChad on my windows machine, but I do have it on linux, and siduck (the creator of nvchad) has given good instructions for installing even on windows, so i don't think it should be a problem. Also, there's a discord for nvchad, and siduck is pretty active on there if you want to ask questions. Good luck!

I update it with Brew on macOS and Scoop [1] on Windows (but I guess it is included in other package managers such as chocolatey).

Of course, a built-in auto-updater would be good, but a packaged version is a nice workaround for me.

[1]: https://scoop.sh/

So I tried installing scoop the "normal" way for both users then ran scoop install {app} --global as per https://github.com/ScoopInstaller/Scoop/wiki/Global-Installs and got:Cannot find path 'C:\ProgramData\scoop\buckets' because it does not exist

There are a number of ways that you can install the Snyk CLI on your machine, ranging from using the available stand-alone executables to using package managers such as Homebrew for macOS and Scoop for Windows.

Scoop provides a wonderful foundation for creating a portable developer's toolkit on Windows systems.