You just need an Apple Developer account ($99/year), which you likely already have if you're distributing apps. Notarization itself has no per-build cost — you can notarize as many builds as you want. The process is essentially: codesign your app, zip it up, submit it to Apple's notary service via xcrun notarytool, and staple the ticket. It can be automated in CI too — this project uses a GitHub Actions workflow for it. The $99/year is really the only cost, and that's for the developer account itself, not notarization specifically.
The git seems to only contain the build of the website with no source code.
The author is probably using git to push the content to the hosting server as an rsync alternative, but there does not seem to be much leaked information, apart from the url of the private repository.
It exposed their committer email (I know its already public on the site, but still)
You can wget the whole .git folder and look through the commit history, so if at any point something had been pushed which should not have been its available
For CLI tools, the program usually only executes for a few seconds and then returns. In this context, you don't even need arena allocators or any memory management at all. You can write the tool in C with malloc and let the OS free the memory at the end without worry.
You could argue with the reasoning that C feels more practical than Zig for real-world CLI tools.
The argument provided by the author feels a bit besides the point.
Yup, but it's more similar to "express" in Node than to a full framework like Django. I have plans to build a library on top of prologue for the ORM and database interaction and other cool features of Django that prologue currently lacks.
For the ecosystem, https://nimble.directory/ is listing quite a few packages. It's still nowhere near the size of the JavaScript ecosystem, but it's a good start.
I'm curious, how much does it cost? Is it per build or a subscription? How do you make it work financially for an open-source project?
reply