RustyCrab on Nostr: One of the biggest problems with C++ utility libraries like poco or the ill-fated ...
One of the biggest problems with C++ utility libraries like poco or the ill-fated boost library is the obsession with defining proprietary types and using them absolutely everywhere. Not only do you make the code unreadable you make it to where including a single header drags in a gigabyte of source code.
I think and hope there must be a project out there that tries to fulfill what they do without being cancerous tumors that kill your compile time
Published at
2023-04-02 13:20:42Event JSON
{
"id": "2f2a4e124de60c94cfb8577c184afd093b2b35051157a7a922594e1ca199170f",
"pubkey": "24ef62ea024bfb5b3e2cdf826d1a5eabf4cef2f792c40c8515bd9eda5967f578",
"created_at": 1680441642,
"kind": 1,
"tags": [
[
"mostr",
"https://sleepy.cafe/objects/0ccee036-8447-4e58-8f1c-9b794401caf7"
]
],
"content": "One of the biggest problems with C++ utility libraries like poco or the ill-fated boost library is the obsession with defining proprietary types and using them absolutely everywhere. Not only do you make the code unreadable you make it to where including a single header drags in a gigabyte of source code. \n\nI think and hope there must be a project out there that tries to fulfill what they do without being cancerous tumors that kill your compile time",
"sig": "248487123a4c147326b2f7f0a19077b0c04657a5bd2ef272a2893c0028d135a91a5a6183cb1432ed34f2b888f700e98fb22048a6fffa4c2bde8a0c66289c2d2b"
}
