Live data from Hacker News

Sparkle: A software update framework for macOS

github.com

81–90 of 128 posts

Re: Sparkle: A software update framework for macOS

#81

Earlier quoted context omitted.

It’s an obvious strawman of arguments in favor of the iOS App Store.

It's not my serious argument, but it's not intended as a strawman. Please, I genuinely would like to know, why do those arguments apply to iOS but not to macOS? Where do you see a strawman in what I wrote?

They don't apply to iOS either. It isn't their device once someone else purchases it. Furthermore, not allowing "sideloading" and bootloader unlocking is wrong. And I'd like to see EU and other governments crack down on Apple following Apple's scummy pseudocompliance with the DMA.

Re: Sparkle: A software update framework for macOS

#82
post #9

Earlier quoted context omitted.

Well the original point is that sparkle predates MAS by more than a decade, and the MAS limitations are a bigger issue than the fees. > Doesn't that leads to the situation on windows where every single app is phoning home at startup? Sparkle has a very clear and regular behaviour, its predictability and widespread use made it easy to manage.

As a more technical user who is aware of Sparkle, I recognise the Sparkle updater and I appreciate it. In fact, I miss this on Windows, where each app updates differently, and most will just throw you annoyingly to the install wizard all over again.

To be fair, Windows Installer can also handle updates (and patches). And proper uninstallation, which is something that’s missing on macOS.

Re: Sparkle: A software update framework for macOS

#83

I write software for Mac and Windows (in C++/Qt). I put each new release out as a separate application for the user to install. Is there some equivalent to Sparkle that runs on both Mac AND Windows, so I don't have to integrate a separate system on each OS? Also I worry about update frameworks as way for bad guys to do bad things via my software. Should I be worried?

Windows installation system is so fundamentally different that it's hard to have a 1-size-fits-all update mechanism. When I shipped a cross-platform application, we used Sparkle on Mac, and a simple utility that downloaded and ran an MSI file for Windows.

In general, I wouldn't worry too much about Sparkle being a vulnerability. It requires that your download servers are hacked: https://9to5mac.com/2017/05/08/handbrake-trojan-mac-malware-...

Re: Sparkle: A software update framework for macOS

#85
post #67
post #34

Earlier quoted context omitted.

> I'd be interested in learning how many average users install software outside of the Mac App Store these days. I'd hazard a guess that Chrome alone would put that figure near 100%

I think you underestimate how many people use Safari.

Nowhere near as how many people use Chrome obviously, even on Mac.

Re: Sparkle: A software update framework for macOS

#86

This makes me somewhat nostalgic for the days when I would regularly encounter software that used Sparkle for updates. The days when I’d mostly use downloadable native software for my Mac. The days when most of the software I regularly used had a somewhat consistent UX.

I miss Adium.

Looking at the git repo, seeing the last commit being three years old is a bit sad. Someone sat down one day created a patch and committed it, and then they went away, to work on other things, leaving the git repository in a digital limbo.

Re: Sparkle: A software update framework for macOS

#87
post #3

Maybe I‘m weird, but for some reason seeing a Sparkle „Update available“ modal popping up fils me with joy (The software I‘m using is getting better) and I enjoy reading the changelog. If there’s some weird custom updater in another software it always fills me with dread because I have to navigate a different UI, and probably have to restart it immediately.

The modal popup is the single thing I can’t stand about sparkle updates. Why oh why can’t they use the regular notification system and respect DND. It always seems so random as well, it’s not when the application starts or quits, just some rando timer polling for updates to surprise me with an interruption I can’t ignore

Re: Sparkle: A software update framework for macOS

#88
post #67

Earlier quoted context omitted.

I think you underestimate how many people use Safari.

Nowhere near as how many people use Chrome obviously, even on Mac.

Data from analytics.usa.gov [1] reveals that Chrome leads browser usage at 48%, closely followed by Safari at 35.7%, highlighting the competitive proximity of Safari to Chrome. Definitely much higher share than I thought.

[1] https://analytics.usa.gov/

Re: Sparkle: A software update framework for macOS

#89
post #83

I write software for Mac and Windows (in C++/Qt). I put each new release out as a separate application for the user to install. Is there some equivalent to Sparkle that runs on both Mac AND Windows, so I don't have to integrate a separate system on each OS? Also I worry about update frameworks as way for bad guys to do bad things via my software. Should I be worried?

Windows installation system is so fundamentally different that it's hard to have a 1-size-fits-all update mechanism. When I shipped a cross-platform application, we used Sparkle on Mac, and a simple utility that downloaded and ran an MSI file for Windows. In general, I wouldn't worry too much about Sparkle being a vulnerability. It requires that your download servers are hacked: https://9to5mac.com/2017/05/08/handbra…

Currently I used Inno Setup to create a .exe installer on Windows and DropDMG to create a .dmg image on Mac.

Presumably Sparkle and Winsparkle both use a similar update mechanism and that doesn't involve full Windows or Mac installers (otherwise, what would be the point?).

Re: Sparkle: A software update framework for macOS

#90

Earlier quoted context omitted.

I miss Adium.

So do I, so often. I made an Adiumy animation pack for my university that actually got mildly popular, and it was amazing. Such a quality app, and so nice when communication systems were standards not apps.

Well, they weren't really standards by design either, people just reverse engineered their protocols. One could still do that, it's just that... nobody does anymore?
Post reply on HN