When the answer to major draw backs with a language is use it better that’s a dead end for me.
Try browsing the list of somewhat recent #CVE rated critical, as I just did to verify. A majority of them is not related to any memory errors. Will you tell all them "just use a different programming language"?
And again with OOP. Why hack it into a language rather than use a language that supports it.
Have you seen existing C code? For anything non-trivial, most code uses some OOP, and it comes quite natural in C, certainly no "hacking". You don't need a class keyword to do that.
If it came out today you’d have an incredibly hard time convincing anyone to use it over other languages.
It doesn't come out today, it's been there for a long time, and it's standardized, proven and stable. Sounds like you seriously misunderstood my points, which were, in a nutshell: For applications and similar, just use whatever suits you; for operating systems do experiments in lab/research projects (as was done with Unix), because existing and established ones are relied upon by lots of software. Just to make that perfectly clear, that doesn't mean they should use C forever, it means they should wait for a potential replacement to reach a similar state of stability with independent standards and competing implementations.
zirias (on snac) /
npub1w9…99l6c
2024-10-04 07:37:37
in reply to nevent1q…2kkn
Author Public Key
npub1w96l7dwwzzmd6taq8qzhgh80hdsad2y0shrank8whyrksa2fkwasz99l6cPublished at
2024-10-04 07:37:37Event JSON
{
"id": "07191f345d1e11b6758b3f75a2c24a1ca85fceb1e3909a8018a259b4664731c5",
"pubkey": "7175ff35ce10b6dd2fa03805745cefbb61d6a88f85c7d9d8eeb907687549b3bb",
"created_at": 1728027457,
"kind": 1,
"tags": [
[
"p",
"6ce2461970e5b1d648ecabd34443b943d0faf3663a97805f46d73ea8460a302d",
"wss://nostr.sprovoost.nl"
],
[
"e",
"19f6cd3708ac8efe6c1051de188ded76e4b94fa42df8c2c4e5e2f0268ad7ec33",
"wss://nostr.sprovoost.nl",
"reply"
],
[
"t",
"cve"
],
[
"proxy",
"https://snac.bsd.cafe/zirias/p/1728027457.405347",
"activitypub"
]
],
"content": "When the answer to major draw backs with a language is use it better that’s a dead end for me.\nTry browsing the list of somewhat recent #CVE rated critical, as I just did to verify. A majority of them is not related to any memory errors. Will you tell all them \"just use a different programming language\"?\nAnd again with OOP. Why hack it into a language rather than use a language that supports it.\nHave you seen existing C code? For anything non-trivial, most code uses some OOP, and it comes quite natural in C, certainly no \"hacking\". You don't need a class keyword to do that.\nIf it came out today you’d have an incredibly hard time convincing anyone to use it over other languages.\nIt doesn't come out today, it's been there for a long time, and it's standardized, proven and stable. Sounds like you seriously misunderstood my points, which were, in a nutshell: For applications and similar, just use whatever suits you; for operating systems do experiments in lab/research projects (as was done with Unix), because existing and established ones are relied upon by lots of software. Just to make that perfectly clear, that doesn't mean they should use C forever, it means they should wait for a potential replacement to reach a similar state of stability with independent standards and competing implementations.\n",
"sig": "674dbf946d14b7956c315209fb22197462074240021bd79d0de32777051375c80a9fe87bf341299c010a877f18ab0b2b5a4da5761897b3544167002fdb6463cc"
}