4 ms·
> Why is your release binary built in debug mode? > Be grateful for what you have. I loved the FAQ overall. But something about this at the end made me bust o
by cosmie 8y ago
> Why is your release binary built in debug mode?
> Be grateful for what you have.
I loved the FAQ overall. But something about this at the end made me bust out laughing.
- KingFelix 8y agoIt is pretty good
- laumars 8y agoThe README in general is inspired. It explains perfectly what it does and the issues it has while making it very clear that it was just a fun side project and does so with quite a bit of humour. It’s a fresh break from those dry READMEs that talk as if their side project will revolutionise they way you use x.
- SiempreViernes 8y agoNo answer about why the sample picture isn't saved as a (static) gif though.
- fouc 8y agoA gif of a gif in a excel spreadsheet? Are you mad?
- userbinator 8y agoA note for the privacy-conscious: binaries built in debug mode may contain more personally identifiable information, including full paths and names. Looking at his profile page, he does not seem too worried about concealing his identity, but it's just something to keep in mind if you want to release something (pseudo-)anonymously.
- ape4 8y agoI wonder if there is an opportunity for a privacy cleaner for executables. Like there is for JPEGs.
- chatmasta 8y agoIndeed, this information often even makes it into the app store. You can sometimes decompile (or run strings on) an app and see a developer's home directory, for example.
- stfwn 8y agoThere is a pitch on the Swift forum to encode only the file name in a binary instead of the entire path, or hash it. The OP there makes some points about file size, even. https://forums.swift.org/t/we-need-filename/ https://forums.swift.org/t/we-need-filename/