251–260 of 515 posts
Earlier quoted context omitted.
It didn’t take my kids long to learn how to run unsigned binaries, and neither of them are developers.
An actual customer won’t like it when you tell them they have to turn off or bypass a security feature to run your software. Not when other software doesn’t need it.
Earlier quoted context omitted.
You don’t have to do any of that for a native Mac app. Signing it is a good idea but not required and you can distribute it from your own website or even from GitHub/Lab where you can tell people it’s not notarized and they’ll need to command click and open it the first time.
> tell people it’s not notarized and they’ll need to command click and open it the first time. That's not realistic for Apple users who are used to ergonomic software. It's not technically required to notarize, but practically speaking, it is.
Earlier quoted context omitted.
> I have to buy developer accounts The Apple Developer Program is only needed for macOS if you want to do sign your binaries or distribute through the Mac App Store. And you only have to pay Microsoft if you want to publish to the Microsoft Store (or use Visual Studio if you're a company that has more than 5 Visual Studio users, more than 250 computers, or more than $1 Million USD in annual revenue). > buy certificat…
If you don't sign your binaries on macOS, the friction for the user to run your app is prohibitive, outside of developer-focused communities.
My opinion about this is that yes, we lost our way, and the reason is very simple, it is because we could. It was the path of least resistance, so we took it. Software has been freeriding on hardware improvements for a few decades, especially on web and desktop apps. Moore's law has been a blessing and a curse. The software you use today was written by people who learned their craft while this free-ride was still ful…
Great take. It feels like the path of least resistance peppered with obscene amounts of resume driven development.
Complexity in all the wrong places.
I want to make native apps but Apple and Microsoft seem to be trying really hard to stop me. I have to buy developer accounts, buy certificates for signing binaries, share 30% of my revenue with them for barely any reason and so on. Not to mention the mess they've introduced in their APIs - especially Microsoft. So of course we choose the much simpler, much cheaper way of the web.
The native world also refuses to create a standard UI API, making everyone use either Qt or Electron because sorry writing it over again for each platform is a hard “no.” Not even big companies do that anymore.
In the early 90s, I believe MS Word came on a few floppy disks and the main executable was 2MB. It ran fine on a 16Mhz 386 with a total of 2MB RAM (let that sink in!) It did pretty much everything it does now, only lacked a grammar checker. (WordPerfect had one.) Now we measure things in GB units. 1000X bigger, but what was gained? We not only lost the way, we don’t even know the destination any more.
Our docker file for running some ML code at work is 6GiB. That does not include the model files. What the fuck, Nvidia? Am I downloading thousands of permutations of generated code for things I’ll never use?
Earlier quoted context omitted.
If you look at the build, yea, it includes everything and kitchen sink. No one cares to parse it down because in most cases, the big GPU servers running this have plenty of hard disk space and since it's a long running container image in most cases, the pull time isn't considered big enough problem for most people to fix. Prime example of "Hardware is cheap and inefficiencies be damned"
If only it was viable to analyze which files get used. Then cut down the image to just what’s needed.
It is interesting to see most people lay the blame at the feet of developers. The reality is that these are all business decisions: 1) Move to the cloud because the business likes the steady payout of subscriptions. Business customers love not having to hire IT teams and demand six 9s of uptime because it is someone else’s responsibility. But performance needs to just be acceptable to end users. 2) Customers refusing…
After a certain period of time, that software worked just fine for those customers. Photoshop is a great example. Sure, you won’t get the flashiest features, but CS4 will still work for you on a Win7 machine without any additional fees paid.
Earlier quoted context omitted.
If you don't sign your binaries on macOS, the friction for the user to run your app is prohibitive, outside of developer-focused communities.
It didn’t take my kids long to learn how to run unsigned binaries, and neither of them are developers.
A lot of it introduced from 2017 onwards and I think now it says something akin to "this application will hack your computer and is a virus" and you need to click the smaller hidden "ignore"s a few times to do what you want.