leah & nybbles & bytes, oh my! on Nostr: one of the worst things about computer language development is that with a few ...
one of the worst things about computer language development is that with a few blessed exceptions, everyone seems to think their shiny new language has to look like C to be acceptable.
C's syntax isn't magic. it's not even that well thought through; Dennis Ritchie openly regretted its declaration syntax, but apparently too late to reverse course in the way he did when he realised that writing the increment operator =+ was a mistake. (incidentally, those operators? came from it being more efficient to implement in the threaded code to which B compiled; they predated both the PDP-11 and, well, C. but they were, nonetheless, not a good idea, sacrificing clarity to terseness.) but it feels like every new language adopts it slavishly, and sprinkles its own mix of shiny sparkles on top of it.
declarations, being things that should only ever be written once, can afford to be loquacious.
for everything else, there's no excuse for writing anything but a name. let the declaration do the work.
Published at
2024-09-03 04:30:14Event JSON
{
"id": "64b29c9439e1835e1894f95c5552babdd7dc9d705d659bd6cbc7e6534fb313e8",
"pubkey": "aa6fb3a41adf045c1169359a7745dfa055b8dec7f9bd7b6dc5160e7ee371a575",
"created_at": 1725337814,
"kind": 1,
"tags": [
[
"proxy",
"https://oldbytes.space/@millihertz/113071739012572430",
"web"
],
[
"proxy",
"https://oldbytes.space/users/millihertz/statuses/113071739012572430",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://oldbytes.space/users/millihertz/statuses/113071739012572430",
"pink.momostr"
],
[
"-"
]
],
"content": "one of the worst things about computer language development is that with a few blessed exceptions, everyone seems to think their shiny new language has to look like C to be acceptable.\n\nC's syntax isn't magic. it's not even that well thought through; Dennis Ritchie openly regretted its declaration syntax, but apparently too late to reverse course in the way he did when he realised that writing the increment operator =+ was a mistake. (incidentally, those operators? came from it being more efficient to implement in the threaded code to which B compiled; they predated both the PDP-11 and, well, C. but they were, nonetheless, not a good idea, sacrificing clarity to terseness.) but it feels like every new language adopts it slavishly, and sprinkles its own mix of shiny sparkles on top of it.\n\ndeclarations, being things that should only ever be written once, can afford to be loquacious.\n\nfor everything else, there's no excuse for writing anything but a name. let the declaration do the work.",
"sig": "ac8083f3fcabcf1b47fbea13dbdd107d94067f466d611a88edc1f36970ccef9479f7d2b491ce1b511f3cb6112294ae93076f1810b026b20dee5dbd8267d3fb8c"
}