News for hackers. Stuff that matters.
Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @12:35PM (#28830155)
I cannot stress how much I do not want a package manager on windows. If it is like chocolatey (optional) I am ok with it, but if it turns out to be like Linux where you install from repos and then you add multiple repos and then you have dependency resolution issues because that's what the package and version needs and the upstream and down stream devs need to sort it out and... ugh that is one part of Linux I hate with passion. I mean it works ok on Linux given who is using it but on windows it is normal, even a requirement for regular users to install apps (repos too in this case). And without AWL , even if you restrict this, people will install "portable" apps.

I like Macos's way best to be honest. Bu this is one practice Windows should not learn from Linux, different audience and requirements.

It looks like yet another competition to chocolatey for now.

Re:Windows Package Manager 1.1 by tempfs on Monday October 11, 2021 @12:42PM (#28830237)
Repos and package management are one of the best features of Linux.

Sorry that you've worked your way into problematic edge cases but for everyone else this solves way more problems that it creates.

A world where you no longer have to update dozens of applications one at a time or worse never at all is a very good thing.

This is also a terrific non-SCCM/Windows Store way to provide access to and limit what all can be installed on a Windows box.

Re:Windows Package Manager 1.1 by OrvalWintermute on Monday October 11, 2021 @01:16PM (#28830592)
I remember how Linux was in the mid 90s. We've come so far and Linux is so much more user friendly.

The first time I used apt on RH I was like wow, this is great!

Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @01:28PM (#28830724)
It was always great, especially when compared to the Windows routine of downloading an installer and running it as Administrator on your server and, for every upgrade, do it again, keeping testing environments to make sure the new version works with the currently applied OS patches and so on.

It was pure pain and anyone who misses those days is either a masochist or has memory issues.

Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @02:57PM (#28831649)
No it is not a way to limit what can be installed? Did you read my comment? Even when I am the admin i alwayd end up having to bypass repos. I get why it is that way for Linux but don't push this on windows.

The problem with how you think is that you expect users to be like you, follow SOPs and all that. This is a help desk nightmare.

AWL already exists in windows (lacks or sucks on Linux) and it can still be bypassed.

The only thing repos create is a walled garden like the apple app store where MS can gate keep who can write code.

Can I write some crappy program and publish it to my friends on a linux distro repo or any appstore? Then how can so many of you on HN that advocate software independence blindly support walled gardens just because it is "Linuxy"?

Re:Windows Package Manager 1.1 by stayfrosty420 on Monday October 11, 2021 @12:45PM (#28830256)
I would hardly call those edge cases, particularly if you use a non-ubuntu distro.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @01:32PM (#28830765)
I’ve been using Red Hat, CentOS, Debian, and Ubuntu servers for the past 20 years and only once I painted myself in a corner with an EPEL RH repo and, even then, I admit it was totally my fault.

I have configured manually dozens of servers, and automatically many thousands, with no significant issues. Only when you fight the distro, you’ll end up caught in an edge case. These things are tested automatically 24x7.

Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @03:00PM (#28831688)
I used Linux for a slightly shorter time and I always fight the distro because it should do what I want not the other way around. I need to get things done, with or without the distros cooperation and in this case with or without MS.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @03:04PM (#28831749)
If you want to get things your way, I suggest using a distro that’s not as opinionated. Arch and Gentoo seem like good options. Never tried Clear or bare-metal Alpine, but I assume they are similar.
Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @04:38PM (#28832779)
I did, not that different. To clarify, I accept things on Linux I just don't want that on windows because it is a mostly solved problem that does not need the complication. It only introduces a false sense of stability. The endless sea of windows software makers will not suddenly stop their development/deployment practices.

I mean on Linux you have the source and everything is debuggable but imagine 10 apps needing 10 versions of the same software. If it comes to this, it will be a fork moment except you can't fork freaking windows!! Stop trying to make windows Linux and Linux windows. They are both great for their uses, this childish war where one or the other needs to be the only way is silly. This silliness is how we have one browser to dictate everyones needs now.

Re:Windows Package Manager 1.1 by tempfs on Monday October 11, 2021 @12:53PM (#28830340)
I use Debian and have three non-Debian repos in my sources.list. No problems thus far.

Been using Linux for over a decade and haven't run into any problems from apt/repo's. So I am using what I believe to be a qualified opinion when I say edge case here.

Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @02:58PM (#28831675)
Even on ubuntu, I run headless servers and this is almost always the case for me. But hey, thanks be to survivorship bias and people jumping on the walled garden bandwagon.
Re:Windows Package Manager 1.1 by jimbob45 on Monday October 11, 2021 @12:52PM (#28830334)
>A world where you no longer have to update dozens of applications one at a time or worse never at all is a very good thing.

Maybe from a storage perspective but storage is practically free these days. It doesn't even make sense from a time perspective since application updating can be done in the background with no kerfuffle.

There's just no advantage to having shared libraries outside of ensuring that you'll eventually break every application on your machine due to some obscure versioning/corruption/capabilities issue that is nigh-impossible for a layman to solve. I'm with the parent poster - Linux can keep its Package Managers to itself (not to say Windows doesn't have equally stupid features - looking at you, Windows Registry).

Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @01:34PM (#28830774)
> There's just no advantage to having shared libraries outside of ensuring that you'll eventually break every application

If an application or service is using a vulnerable outdated library, I WANT it to break. It’s better to have it broken than have it expose sensitive user data.

Re:Windows Package Manager 1.1 by jimbob45 on Monday October 11, 2021 @02:01PM (#28831048)
Hard disagree. I'll decide which applications I want updated and when. I don't need my applications breaking because someone decided I'm not allowed to use it anymore.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @03:10PM (#28831815)
We don’t have the luxury to decide when we will get hacked.
Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @11:13PM (#28835681)
That's not how security risk assesment work. You do get to decide when and how long you remain hackable and implement mitigating security controls. Not everyone has the luxury of being tolerant to outages and it is terrible security practice to take a forceful uncompromising approach like that with no consideration to why and how the software is being used and in what context.

The last thing you want in securing a system is for your securitu effort itself to be a security risk (availability)

Re:Windows Package Manager 1.1 by ASalazarMX on Monday October 11, 2021 @01:03PM (#28830461)
> then you have dependency resolution issues because that's what the package and version needs and the upstream and down stream devs need to sort it out

I think your problem is that you're adding too many third-party repos. The distribution repos can be severely outdated, maybe even buggy, but fortunately most third-party repos are not troublesome. If you have one that is, don't add it, try an alternate installation medium, or consider a different application.

Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @01:37PM (#28830812)
> The distribution repos can be severely outdated, maybe even buggy

They may be outdated (as in RHEL or Debian Stable) but even old versions get regular bug fixes. And RHEL and Debian and its family pretty much run the world (except the parts written in COBOL running under CICS and z/OS)

Re:Windows Package Manager 1.1 by ASalazarMX on Monday October 11, 2021 @02:25PM (#28831284)
Buggy includes non-security bugs, like a flaw in the UI that upstream already corrected in a newer version, or a feature you need that was compiled out by the packager.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @03:08PM (#28831798)
In that case, I’d suggest either paying someone to backport the fix and offer it to the distro, or rolling your own repo with your package and a minimal set of dependencies (the more minimal, the better) and live with your almost-distro. The beauty of open source is that you can always work your way out of a situation.
Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @11:15PM (#28835689)
Yes, and can you imagine a windows install by regular users without too many 3rd party repos? If you do then I suspect you may not understand how vast and complex the software ecosystem is in Windows land.
Re:Windows Package Manager 1.1 by e12e on Monday October 11, 2021 @12:39PM (#28830192)
> I like Macos's way best to be honest

App store/package manager gatekept by vendor + random binaries from the internet?

Re:Windows Package Manager 1.1 by fabioborellini on Monday October 11, 2021 @01:01PM (#28830443)
You forgot to mention the horribly slow, unreliable and opaque pile of Ruby scripts that users tend to herd these random binaries with.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @01:38PM (#28830821)
Or you can use MacPorts, which is rock solid and never borks your machine.

I really don’t know why people use anything else.

Re:Windows Package Manager 1.1 by jamesgeck0 on Monday October 11, 2021 @05:16PM (#28833193)
I’m not overly fond of MacPorts dependency on the full-fat Xcode instead of just the Xcode CLI tools.
Re:Windows Package Manager 1.1 by rbanffy on Monday October 11, 2021 @05:35PM (#28833389)
I’d rather have Xcode than something messing with my /usr/bin folder.
Re:Windows Package Manager 1.1 by curt15 on Monday October 11, 2021 @01:31PM (#28830757)
Installing software on MacOS is only convenient when it is distributed as self-contained .app bundle. Only self-contained GUI apps are distributed this way. Managing software that comes in ".pkg" files is strictly worse than using Linux packages. Unlike on Linux, there is no dependency tracking or interface for un-installing such software.
Re:Windows Package Manager 1.1 by Isthatablackgsd on Monday October 11, 2021 @12:53PM (#28830348)
> I like Macos's way best to be honest.

Apple App store or the package manager?

Apple does not have a package manager from my understanding and I uses macOS daily. I don't like the approach with the App Store since there are some FOSS that are charging a fee to use their apps in the App Store. I understand it was due to Apple's Developer fee. App Store is not a package manager, it is an application online store in the same vein with Google Play Store & Microsoft Store.

If you are talking about the package manager, then which manager you are referring to? Brew, MacPorts, Nix? I uses Brew daily and only once have to add one repo (using MBA for less than a year) due to external plugin that the app use which it's easy to add in the command line.

Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @05:51PM (#28833506)
Dmg images is what I meant. Very user friendly, you can download and run one from the vendor site too.
Re:Windows Package Manager 1.1 by invokestatic on Monday October 11, 2021 @12:44PM (#28830248)
Windows has a manifest system for shared libraries that allow multiple versions of a library to coexist side-by-side. My hope is that this alleviates problems.
Re:Windows Package Manager 1.1 by michaelmrose on Monday October 11, 2021 @02:10PM (#28831132)
This is an example of a comment that is I think incorrect in a few different respects already reasonably explained in replies however its not rude or poorly written and in fact although incorrect in my opinion it prompted useful discussion.

This is an example where down vote to disagree isn't useful because instead of discouraging people from expressing opinions you believe are wrong a fruitless endeavor you may actually be discouraging the useful discussion that follows.

Re:Windows Package Manager 1.1 by kjaftaedi on Monday October 11, 2021 @04:35PM (#28832750)
It didn't prompt any useful discussion though as there are no other participants on the "package managers are evil" side

It might be useful to the commenter, but to the community it is not.

Re:Windows Package Manager 1.1 by badrabbit on Monday October 11, 2021 @11:18PM (#28835702)
I did not claim package managers are evil. I only claimed they are a bad fit for windows if if their usage is mandated because of the specifics and nuances of the windows software ecosystem which isn't exactly similar to the FOSS ecosystem.
Re:Windows Package Manager 1.1 by michaelmrose on Tuesday October 12, 2021 @02:21PM (#28843170)
I think a fundamental misunderstanding is conflating Linux style system package management

A collection of resources that are inserted and removed into standard locations plus metadata used to retrieve additional resources many times including some that may be shared between multiple packages including but not limited to dynamically linked libraries and actions to be completed on addition or removal of a package.

and the fundamental concept of a package manager

A tool that provides a standardized set of steps easily add or remove one or more resources to or from a system from a previously configured set of sources without the user needing to manually attend to the details of each installation.

A package manager doesn't inherently impose any sort of constraints on how such packages are retrieved, their requirements met, or their operations actuated. It is the simple mapping between clicking or typing install foo bar in a singular interface and foo and bar being installed on your system. Foo and Bar could be msis individually retrieved from their respective web pages each bundling 100% of the resources needed to run and depending on nothing outside themselves. That is to say the result of running install foo bar could be the EXACT same result as navigating to each respective website, finding the appropriate download, running the installer, answering any questions, disabling any adware or toolbars and waiting for each routine to finish save only that you can't accidentally install malware, you don't need to google the website, its trivially repeatable and suitable to automation.

In that context even if you don't like Linux system package managers it is incorrect to reject package managers in general as they are strictly superior to the alternative of manually retrieving the same packages to the web and in no way impose the things you dislike about Linux system package managers that you are concerned about.

Although you may competently perform that task in fact the act of retrieving and installing software is one of the largest source of infections among users. Removing this source of challenges is as useful as the time saved by being able to run install foo.

Re:Windows Package Manager 1.1 by bombcar on Monday October 11, 2021 @12:36PM (#28830170)
Package managers are wonderful if you stick with what your distribution packages.

But once you step outside of that it can get fun real fast.

And many things now basically do what Apple does anyway and bundle all libraries, etc with each app - Go does this explicitly I think. Space is cheap.

Re:Windows Package Manager 1.1 by Isthatablackgsd on Monday October 11, 2021 @01:03PM (#28830467)
> Space is cheap.

That is subjective. Yes generally the drive storage is cheap. Apple storage in other hands are not cheap at all and charging a premium for it. Looking in MacBook Pro catalog, they are charging $200 for 513 GB SSD to 2 TB for $800. Most of the SSD of that range is in $50 - $150 USD. Drive storage is cheap, Apple storage are not cheap.

Re:Windows Package Manager 1.1 by bombcar on Monday October 11, 2021 @01:40PM (#28830845)
Even at those inflated prices storing Google Chrome itself is $0.20. Most libraries aren't 500mb.
Re:Windows Package Manager 1.1 by tinus_hn on Monday October 11, 2021 @01:46PM (#28830908)
If you want to use your device for about 6 years, you have to consider how big these apps are going to be in 6 years. Google Chrome is not going to be 50mb in 6 years.
Re:Windows Package Manager 1.1 by bombcar on Monday October 11, 2021 @03:03PM (#28831739)
It's 500MB today; would be fun to see a graph of how it has changed over time. It looks like Chrome 1 was 9MB (for Windows)
Re:Windows Package Manager 1.1 by tinus_hn on Monday October 11, 2021 @01:44PM (#28830887)
Wasting somebody else’s space is cheap, especially if you’re the one selling them extra space.