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...
Reviving a 16-year-old Mac App
51–60 of 108 posts
Re: Reviving a 16-year-old Mac App
#52Earlier 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…
Re: Reviving a 16-year-old Mac App
#53You can still do that.
Re: Reviving a 16-year-old Mac App
#54> 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…
Re: Reviving a 16-year-old Mac App
#55> In 2003, you could switch the config to Release, hit build, zip the app, and then put on a web server. You can still do that.
Re: Reviving a 16-year-old Mac App
#56Every 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.
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…
Re: Reviving a 16-year-old Mac App
#58Earlier 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…
Re: Reviving a 16-year-old Mac App
#59Earlier 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?
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
#60The 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'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.