Live data from Hacker News

Reviving a 16-year-old Mac App

blog.tumult.com

51–60 of 108 posts

Re: Reviving a 16-year-old Mac App

#51

Every modern web framework has auto reload, so this is an app that’s only targeting people who know HTML well enough to hand write a page but don’t know about modern web development. Good luck, but I can’t imagine it’s a growing market.

Or developers who want to write basic HTML webpages without use of any of the bloated modern frameworks...

Right, sometimes you just want a web page, and not a web app.

Re: Reviving a 16-year-old Mac App

#52
post #47

Earlier quoted context omitted.

It’s so frustrating that automation and command-line is treated as almost second-class citizenship on macOS. You know how I log into a remote server securely without ever entering my password? I enter the command "ssh" and the server name. Why the hell isn’t notarization implemented, effectively, as "notarize appname.app" where all the details are resolved securely, just as magically, to your developer keys? Yet if y…

A year or so back I wrote a little ffmpeg concatenation helper to make a friend's life easier. It was an OK shell script but it needed a config file to list all of the files that needed concatenation, and I wanted to just make a GUI that would let her add and reorder files to a list, then generate a temp file with the list (ffmpeg required the list to live in a file for some reason) and fire off the ffmpeg command to…

Unless you wanted to submit this to the Mac App Store, you could have just turned off sandboxing. With that off, the only permission required would be Catalina’s permission dialogs when any app first accesses various folders (Documents, etc.), and those are automatic without needing any code in the app to request them.

Re: Reviving a 16-year-old Mac App

#54
post #5

> I don’t think it is an exaggeration to say the amount required to learn to distribute software exceeds the amount I needed to know to write the first beta of HyperEdit! I wonder if it would have gotten off the ground if I started today. This mirrors my feeling. It might be easier to learn to program say TypeScript or Go today than it was to learn php or C in the late 90s, but actually creating a complete program, d…

You can blame the rise of authoritarianism (for lack of a better term) and centralised control, which Apple has been very good at. The increasing bureaucracy is ultimately beneficial to Apple's bottom line.

Re: Reviving a 16-year-old Mac App

#56

Every modern web framework has auto reload, so this is an app that’s only targeting people who know HTML well enough to hand write a page but don’t know about modern web development. Good luck, but I can’t imagine it’s a growing market.

I build my website with Jekyll 4 and use livereload, but have actually found some use out of this tool for writing small snippets. Seeing your CSS come to life with every keystroke in real time (without having to press CMD+S in your IDE) is surprisingly useful.

The main use-case where this tool has been useful, though, is when I'm working on my Mac app that uses WKWebView and Javascript pretty extensively. It's much faster to get little JS snippets right compared to the really slow build+run cycle in Xcode.

Re: Reviving a 16-year-old Mac App

#57

> In 2020, distributing requires learning the intricacies of certificates, code signing, provisioning profiles, hardening, notarization, .dmg creation, gatekeeper, and paying a $99 per year fee. I had to manually create, sign, and notarize a Mac app the other day and it was total madness. It took multiple tabs of Apple documentation ( new documentation, I might add, created this year because everyone complained last…

It’s so frustrating that automation and command-line is treated as almost second-class citizenship on macOS. You know how I log into a remote server securely without ever entering my password? I enter the command "ssh" and the server name. Why the hell isn’t notarization implemented, effectively, as "notarize appname.app" where all the details are resolved securely, just as magically, to your developer keys? Yet if y…

Especially given how Mac was at one point ahead of everyone else in terms of automation...

Re: Reviving a 16-year-old Mac App

#58
post #39

Earlier quoted context omitted.

TIL. I thought this was just so that all apps are in one place for ease of access. When I first tried OS X in the form of hackintosh around 2009, most apps were already distributed in dmgs with "drag to install" so I just thought it's a very neat, Apple-ish way (ugh Windows install wizards) and assumed it's always been like that. Older PPC Macs were basically never really a thing where I'm from. Now I remember seeing…

> Anyway, with all these Gatekeeper changes, it's almost as if Apple doesn't want non-app-store apps at all. Of course that's their idea, The Mac Store has been a moderate failure, so now they are pushing people into it slowly more and more every release. As Apple and Microsoft (with their Windows Store) have learned, if there's a real choice between an app store and a standard install, nobody will pick the app store…

Heh, I actually prefer the app store version wherever I can download it, because I like not having to think about updates; I let the software updater do it. Is this an uncommon attitude?

Re: Reviving a 16-year-old Mac App

#59
post #58

Earlier quoted context omitted.

> Anyway, with all these Gatekeeper changes, it's almost as if Apple doesn't want non-app-store apps at all. Of course that's their idea, The Mac Store has been a moderate failure, so now they are pushing people into it slowly more and more every release. As Apple and Microsoft (with their Windows Store) have learned, if there's a real choice between an app store and a standard install, nobody will pick the app store…

Heh, I actually prefer the app store version wherever I can download it, because I like not having to think about updates; I let the software updater do it. Is this an uncommon attitude?

Developers care a lot about updates, your average user does not. For them, an update means there's a chance the app isn't going to work like it used to be.

People went as far as disabling all windows updates manually.

Also as a second point, you can totally have a software updater without an app store.

Re: Reviving a 16-year-old Mac App

#60
post #3

The old app really still looks quite nice. Even windows 98-era apps look pretty good in a way. One part of me doesn't like how much space is wasted by the new Mac UI trends shown in the second screenshot, mostly the left side panel. But I understand screens are different these days as well.

I think Mac apps have settled into a pleasant place for the most part, though I'm not a fan of the look of Apple's newer apps like the App Store and News.

I'm glad that the brighter colors are more subdued now, annoying UI elements like drawers and palette windows have mostly been replaced by inspector panes, and brushed metal is long gone.

Post reply on HN