News for hackers. Stuff that matters.
Re:Tea: A new package manager from the creator of brew by Nicksil on Sunday November 20, 2022 @11:33AM (#33682364)
>the majority of its users (developers) want rolling updates for their tooling.

I haven't met a single software developer who wants this. That's not to say your statement is incorrect -- I have no evidence stating otherwise -- but the idea boggles my mind.

Re:Tea: A new package manager from the creator of brew by mattarm on Sunday November 20, 2022 @11:42AM (#33682493)
Please allow me to introduce myself...

Pleased to meet you Hope you guess my name But what's puzzling you Is the nature of my game

Re:Tea: A new package manager from the creator of brew by cle on Sunday November 20, 2022 @11:55AM (#33682656)
A huge amount of Linux users use rolling release distributions now (Arch, Manjaro, EndeavourOS, etc). I prefer it as well because I find it less disruptive than occasional big-bang versioned releases.

Where versioning matters, we have better tools than OS package managers now (ex Docker).

Re:Tea: A new package manager from the creator of brew by akerl_ on Sunday November 20, 2022 @11:56AM (#33682668)
I want rolling updates for my tooling.
Re:Tea: A new package manager from the creator of brew by 95014_refugee on Sunday November 20, 2022 @12:41PM (#33683182)
> I haven't met a single software developer who wants this.

You should get out more. No offense.

Incremental pain, delivered early, is both corrective and less expensive over the long run. If you need to remain version-locked for a specific reason, that reason is likely to be locally scoped rather than global, in which case TFA describes an attempt to address your problem.

Re:Tea: A new package manager from the creator of brew by Nicksil on Sunday November 20, 2022 @12:58PM (#33683353)
>You should get out more. No offense.

This is an unnecessary comment.

>Incremental pain, delivered early, is both corrective and less expensive over the long run. If you need to remain version-locked for a specific reason, that reason is likely to be locally scoped rather than global, in which case TFA describes an attempt to address your problem.

This rests on the assumption of a relatively homogenized software development industry without any consideration for, at least, critical systems building. There's a broad range of disciplines in this industry which do not -- and cannot -- adhere to the practices you mention.

Re:Tea: A new package manager from the creator of brew by spmurrayzzz on Sunday November 20, 2022 @12:41PM (#33683185)
I am also in the camp of engineers who prefer stability over bleeding edge. But I do understand folks who prefer the latter modality. If dependencies are gonna break, often its more desirable to have them break quickly with a short remedial cadence to follow. In my own anecdotal experience though, "short" is probably too charitable of a descriptor for the time to fix.
Re:Tea: A new package manager from the creator of brew by rleigh on Sunday November 20, 2022 @12:47PM (#33683226)
I'd much prefer a compromise, like the FreeBSD quarterly updates vs daily, so you can pick the update frequency.

I can't tell you the total number of wasted hours my previous organisation spent upon maintaining MacOS infrastructure after random breakage due to homebrew, but it was a regular occurrence and likely a few hundreds of hours per year for the small setup we looked after, mainly for CI.

Re:Tea: A new package manager from the creator of brew by jemmyw on Sunday November 20, 2022 @03:13PM (#33684784)
For tools that I develop on I use asdf for versioning. For everything else I want the latest stable version, so homebrew works well.

On Linux I use a rolling release distro for the same effect.