[drnick1]

> Increasingly software is distributed by "curl dodgysite.com/get.sh|sudo bash -"

I don't think this is the norm at all. I have seen curl/bash install scripts for tools like Claude Code, but they don't use sudo, and the expectation is that you deploy them in isolated user accounts or containers.

[iso1631]

== Docker ==

Docker provides a convenience script at https://get.docker.com/ to install Docker into development environments non-interactively.

== Homebrew ==

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/inst...)"

Paste that in the macOS Terminal, a Linux shell or WSL. The script explains what it will do and then pauses before it does it. Read about other installation options.

== k3s ==

K3s provides an installation script that is a convenient way to install it as a service on systemd or openrc based systems. This script is available at https://get.k3s.io. To install K3s using this method, just run:

These scripts have lines like

> abort "Need sudo access on macOS (e.g. the user ${USER} needs to be an Administrator)!"

> # --- use sudo if we are not already root ---

[zen928]

> the expectation is that you deploy them in isolated user accounts or containers.

Why are you lying right now? This is a norm across the dev tools world for businesses to distribute dodgy curl piped to bash scripts that users install without question, popular examples: homebrew, docker, nvm, bun, deno, k3s. There is zero "expectation" given by any of these install scripts that they are isolated. Can you even find a single source online that suggests doing what you said for you to think its a commonly held expectation?

[drnick1]

> Can you even find a single source online that suggests doing what you said for you to think its a commonly held expectation?

Isn't it common sense? Do you want coding agents to read and possibly upload somewhere the contents of your home directory?

Also, the expectation on Linux is that you install tools like Docker from the distro's repos.