pistolero on Nostr: Haelwenn /элвэн/ :triskell: Q.U.I.N.N. > Except you can actually target C89, ...
Haelwenn /элвэн/ :triskell: (npub1ysu…2jyl) Q.U.I.N.N. (npub1f8e…zu5u) > Except you can actually target C89, it's an explicit version of a standard, not an implementation.
You can target Lua 5.1.
> And in fact I think putting -std= in compiler flags should be nearly mandatory for build stability reasons as stuff gets deprecated over time and the default version changes over time for at least GCC and clang.
Duct-taping around instability rather than pushing back against it gets you the same fate that Ruby and Python and Linux got. Stable APIs beat version-coupling every single time. Every single time. Zero exceptions. Once you introduce version-coupling, upstream starts breaking shit, and in terms of behavior that you can depend on, the cycles get faster than they were without any versioning.
Published at
2024-01-05 17:00:08Event JSON
{
"id": "f70a505b42ae90d876482684b5a22fcbdcd1a76989c879eb214701b61f18a354",
"pubkey": "c5cf39149caebda4cdd61771c51f6ba91ef5645919004e5c4998a4ea69f00512",
"created_at": 1704474008,
"kind": 1,
"tags": [
[
"p",
"24389949b53d16958eae22ba78a4040316903c933a9e8f9d9fd5f10688fc62af",
"wss://relay.mostr.pub"
],
[
"p",
"49f3a746c8d602bb57f2fbcbcec59910fc8742b2c71c4609b3091709fc2a2375",
"wss://relay.mostr.pub"
],
[
"e",
"6e83d6c0515462ebbba4c95391b67a9cd0d16687fdd8e3ba52d24282448ac555",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://freespeechextremist.com/objects/611a40df-f4a8-4055-aa3f-b6addb3368be",
"activitypub"
]
],
"content": "nostr:npub1ysufjjd485tftr4wy2a83fqyqvtfq0yn820gl8vl6hcsdz8uv2hskx2jyl nostr:npub1f8e6w3kg6cptk4ljl09ua3vezr7gws4jcuwyvzdnpytsnlp2yd6savzu5u \n\n\u003e Except you can actually target C89, it's an explicit version of a standard, not an implementation.\n\nYou can target Lua 5.1.\n\n\u003e And in fact I think putting -std= in compiler flags should be nearly mandatory for build stability reasons as stuff gets deprecated over time and the default version changes over time for at least GCC and clang.\n\nDuct-taping around instability rather than pushing back against it gets you the same fate that Ruby and Python and Linux got. Stable APIs beat version-coupling every single time. Every single time. Zero exceptions. Once you introduce version-coupling, upstream starts breaking shit, and in terms of behavior that you can depend on, the cycles get faster than they were without any versioning.",
"sig": "d99110db58b32406f63c3b78556430c7cae27808302d9f3f78a624cee0e988d8aed6576451e4906ebb6f3c6d32cc529ab420fb096f331b054db24fc387112e0e"
}