zlacker

[parent] [thread] 4 comments
1. llm_ne+(OP)[view] [source] 2026-02-06 09:35:17
It is literally the method given to install a number of products. The first mechanism given as a fix, of sorts, is to install something via brew.

Brew is installed by copying a command line-

https://brew.sh

I mean, I guess you could retype it, but there is no intention for anyone to do that.

replies(2): >>kreetx+Sg >>steve1+Gx
2. kreetx+Sg[view] [source] 2026-02-06 12:11:10
>>llm_ne+(OP)
While true, then I'd just skip installing these products and find another way. And if this is the only way and the product is important (say, brew), make an exception.
3. steve1+Gx[view] [source] 2026-02-06 14:00:28
>>llm_ne+(OP)
I think Homebrew still makes a mess with permissions on multiuser systems (at least on macOS), so it's probably not a good example of best practices.
replies(1): >>llm_ne+UT
◧◩
4. llm_ne+UT[view] [source] [discussion] 2026-02-06 15:49:20
>>steve1+Gx
I'm not holding it as a best practice, and I don't see how that was interpreted from my comment. I think installation through a copy/pasted script is terrible business.

But it was held as something exceptional, when here in reality a number of extremely widely used products, frameworks and tools provide installation through a curled shell script command.

Another example is CUDA on Linux. Installed via some copy/pasted scripts from a webpage.

replies(1): >>steve1+4Y
◧◩◪
5. steve1+4Y[view] [source] [discussion] 2026-02-06 16:06:02
>>llm_ne+UT
I have must misunderstood or misinterpreted your comment a bit then.

I fully agree, this seems to be becoming more and more common unfortunately.

[go to top]