Matt Campbell on Nostr: It's tempting to reduce the compiled size of one's software by excluding debug info ...
It's tempting to reduce the compiled size of one's software by excluding debug info from release builds. For end-user apps, it makes sense to exclude the debug info from the main distribution, and for proprietary software, to keep it to oneself. But for pre-built binaries of open-source libraries, like my #AccessKit project, I think we have a duty to include debug info in the build and pass it along, so the ultimate app developer can debug issues in release builds if they need to. Thoughts?
Published at
2023-12-30 15:52:58Event JSON
{
"id": "03d5871dc8242af05d11ef6621ae74c31d6cc0f8638044b86b55ddbb0e5acf9e",
"pubkey": "790e5e1a77f369f0eae0afb55dd1fae16c51eb87977c87a9b4fa113c6bac5399",
"created_at": 1703951578,
"kind": 1,
"tags": [
[
"t",
"accesskit"
],
[
"proxy",
"https://toot.cafe/users/matt/statuses/111670170622437123",
"activitypub"
]
],
"content": "It's tempting to reduce the compiled size of one's software by excluding debug info from release builds. For end-user apps, it makes sense to exclude the debug info from the main distribution, and for proprietary software, to keep it to oneself. But for pre-built binaries of open-source libraries, like my #AccessKit project, I think we have a duty to include debug info in the build and pass it along, so the ultimate app developer can debug issues in release builds if they need to. Thoughts?",
"sig": "ddb955c47bd68584d5aebc0024851549252c96328383aa388473e62629259af601d3091214bad00dd6d489e514fa11adc75bfa658055bb96b348b294d7d05ded"
}