Live data from Hacker News

“I just chose words carefully”

unsung.aresluna.org

311–320 of 374 posts

Re: “I just chose words carefully”

#311

In programming certain word choices are valuable in this way. It's sad that pairs like true/false, good/bad, first/rest, and left/right are unequal length. But there are nice pairs like old/new, head/tail, fast/slow, same/diff, and right/wrong, which can help with create natural vertical alignment throughout a function.

> old/new, head/tail, fast/slow, same/diff, and right/wrong also some abbreviations work fine: min max row col beg (vs start) end key val src dst pos len and we have public_key secret_key (vs private) from till push pull load save init done inner outer ----- and if you speak Norwegian you have two options: ja yes no nei but that may trigger a different kind of OCD :-)

There's also aye/nay but I don't think I've ever seen those in code

Re: “I just chose words carefully”

#312
post #65

Earlier quoted context omitted.

I'd argue that "le" is not really phonetic to how people pronounce words ending in that; "missils" would be more phonetic

> I'd argue that "le" is not really phonetic to how people pronounce words ending in that Sorry? How do you think people pronounce words such as truffle / turtle / tremble / pickle / maple / rubble / etc. etc. etc.?

I think they pronounce them non-phonetically, and I'm not really sure what's confusing about that. Pronunciation differing from spelling is literally what it means to say something isn't phonetic; if I accepted the spelling of other non-phonetic words as proof that something is phonetic, then everything by definition would be phonetic, and the entire concept would be pointless.

In my mind, the natural phonetic spelling of "le" is an L sound followed by an E sound. Works like "truffle" and "turtle" have an E sound followed by an L sound. I don't think that's phonetic.

Re: “I just chose words carefully”

#313

The maintainer of top fully-justifies his commit messages, e.g., https://gitlab.com/procps-ng/procps/-/commit/e6f22569e9db16d ... commit e6f22569e9db16dbef7d9bdee5bb41b8cb7a03ca Author: Jim Warner Date: Tue Jul 23 00:00:00 2024 -0500 top: attempt once again to allow help text translation Back when our release 4.0.1 was being readied, sources were sent to the TP (Translation Project). However one person named Benno Sc…

I too feel that fully justified text can be fully justified. I used to use it back when blogs were a thing.

Re: “I just chose words carefully”

#314

Earlier quoted context omitted.

> I'd argue that "le" is not really phonetic to how people pronounce words ending in that Sorry? How do you think people pronounce words such as truffle / turtle / tremble / pickle / maple / rubble / etc. etc. etc.?

Conversations like this are a dead end. You can't devise a phonetic spelling convention without using a phonetic alphabet. The reason you think that "le" makes sense and the person you are responding to thinks otherwise is that in English, the pronunciation of "le" isn't phonetically consistent. I imagine that GP's reasoning is that in writing "missile", the consonant is followed by a vowel, while phonetically the vo…

> Conversations like this are a dead end. You can't devise a phonetic spelling convention without using a phonetic alphabet.

I don't disagree with the latter point, but the former doesn't make sense to me; unless you're saying that there wouldn't be enough phonemes representable by the letters to define spellings for all English words? In my mind, the entire point of a conversation like this is hypothetical changes to the language to make it phonetically consistent; of course it isn't right now, or we wouldn't need to have a conversation.

You've correctly identified what my reasoning is, but you seem to be circularly saying that since English isn't currently phonetic, it's impossible to come up with a spelling for it using sounds that roughly resemble the common sounds letters are using today in order to make it phonetic. I guess I don't know that it's literally impossible, but I don't think it's self-evident that it's not possible, and I think it's fairly straightforward changing the spelling of words ending in "le" to "el" would be more consistent to how "le" is used in other places in words where changing their spelling would be more difficult (e.g. there's not really any clear way to spell "less" without preserving "le" at the beginning).

You're definitely right that I hadn't considered that some dialects pronounce "missile" in a way where it's pronounced differently, but I'd argue that the obvious example (British pronunciation) was already basically ignored by the comment I was responding to, so I didn't really introduce the inconsistency.

Re: “I just chose words carefully”

#315
post #65

Earlier quoted context omitted.

I'd argue that "le" is not really phonetic to how people pronounce words ending in that; "missils" would be more phonetic

> "missils" would be more phonetic Only for Americans. In British English, it's "MISS isle", and "MISSul" is a church book. I'm not Christian and I am not sure of exactly what's in a _missal_ but it's prayers or something. I do not know if American English even has missals. They're old fashioned things these days, I think. But in my dialect, "missile" and "missal" are two different words with 2 different sounds, whic…

I was responding to the framing of the parent comment that suggested "missles", which already essentially ignored that pronunciation.

Re: “I just chose words carefully”

#316
Douglas Hofstadter, Le Ton beau de Marot (1997), pages xviii–xix:

> Because I have always had a very clear sense of how thing should look on a page, I dearly wanted to be able to control every tiny detail of my book's overall look, ranging from the cover art to the typefaces used to the size of the pages to the way displays are indented, and so on. Fortunately, the people at Basic Books have grown used to me and my idiosyncrasies over the years I have worked with them, and they assented to my unusual request.

> [new page] Consequently, I have enjoyed total control over such things as line-breaks, page-breaks, hyphenations, widows, orphans, density of word spacing within lines, fine-grained intercharacter spacing ("kerning"), and so forth and so on — things that most people usually are unaware of and simply leave to their publisher or their word processor. I am a fanatic, though, and these things matter a great deal to me. Not only do they matter to me, they have had an overwhelming impact on this book from start to finish. This may sound crazy, but it is the gospel truth.

> [section heading] Who Is Really Controlling Whom?

> Above, I very casually remarked that I have enjoyed total control over page-breaks and such things; yet the truth of the matter would be far more accurately captured by turning the phrase around and saying that the page-breaks and word spacing and such things have enjoyed total control over me! By this, I mean that I have been forced to rewrite and rewrite and rewrite passages in order to make a page boundary come out exactly where I wanted it. It is not just by some happy accident, for instance, that the poems inside chapters are never, ever broken across page boundaries.

> The amount of influence exerted on my text by concerns of purely visual esthetics is incalculable — and by "my text", I don't merely mean how I wound up phrasing my ideas, I mean the ideas themselves. Content has been determined by considerations of elegant form so often that I couldn't begin to imagine it. Every single line of text, for instance, is characterized by its spacing — how wide the blanks between words are. I can clearly see the spacing as I type on my screen, and I rewrite and rewrite in order to make sure that no line is too tightly or too loosely spaced. In the course of such rewritings — here extracting a word, there using a shorter or a longer one, elsewhere inserting a word where none was — words and phrases that I would otherwise not have thought of pop to mind, suggesting ideas I would not have thought of, and those ideas suggest unexpected paragraphs, and those paragraphs are in turn linked to other ones, and so on...

Re: “I just chose words carefully”

#317
post #148

In programming certain word choices are valuable in this way. It's sad that pairs like true/false, good/bad, first/rest, and left/right are unequal length. But there are nice pairs like old/new, head/tail, fast/slow, same/diff, and right/wrong, which can help with create natural vertical alignment throughout a function.

In Japan they have the abbreviation “NG” (“not good”) that’s often used as the opposite of “OK”. I always liked how, when I worked for a Japanese machine learning company, classifiers would be between “OK” and “NG”. Maybe semantically “okay” and “not good” are not great opposites, but I always liked how having textual alignment makes the contrast immediately obvious

Is this not common outside of Japan? I've often seen this used here in Canada.

Sometimes as NFG after a particularly bad day.

Re: “I just chose words carefully”

#318

Almost irrelevant to the story itself, but here's what it feels like to use Emacs these days. The story talks about monospace fonts and how unappealing they could be for reading prose. It is a fascinating post on itself, but here's what happened - it caught my eye while I was busy, I clicked the link, it opened the page, I kept it hanging around and forgot about it. Then HN page got buried in my browser history. Afte…

This is why so many of us are so much into Emacs. In a time where pretty much all software around us gets progressively enshittified, there’s this 50 year old Lisp interpreter masquerading as an editor that you can make truly and uniquely yours.

Yup. Watching so many of my peers struggle with some basic tasks like grabbing a url and inserting it into a chat buffer. I mean, come on. How many times a day you do this? And you just settled with always:

- going back to the browser

- clicking on address bar

- attempting to select the link with the mouse

- switching back to wherever you want the link

- inserting it

- realizing that you missed a character - mouse is imprecise for text selection

- repeating the process

- Oh shoot. It's a markdown, I need now to grab the description of the page too. And... back to the dance again.

Shit like this, for me is just pressing a key. And it nicely formats it (for whatever markup you want), grabbing the correct description, etc. I solved the problem once, and it just works and I never have to ever spare a split second neural signalling for it - there's no attention tax.

I'm forever indebted to my younger self for convincing and forcing myself to learn Lisp and spend some time understanding Emacs. Among all sorts of skills that I picked up during my tenure - CLIs, Unix, Linux internals, networking, git fundamentals, vim, various programming languages, front-end, devops, cybersec, etc. etc. - Lisp remains enormously practical, the best skill that I'm so glad I acquired.

Re: “I just chose words carefully”

#319
post #279

Earlier quoted context omitted.

It seems to wrap correctly in landscape mode.

Newspapers figured out wide text lines are awful for reading some 100 years ago. We're still waiting for web designers to catch up...

Narrow columns leave more room for ads. Ads that aren't even slightly aligned with products you're interested in.

Re: “I just chose words carefully”

#320
post #277

Earlier quoted context omitted.

What does KO stand for?

What does OK stand for?

  The origin of OK is disputed; however, most modern reference works hold that 
  it originated around Boston as part of a fad in the late 1830s of 
  abbreviating misspellings – that it is an initialism of "oll korrect" as a 
  misspelling of "all correct". This origin was first described by linguist 
  Allen Walker Read in the 1960s.
  
https://en.wikipedia.org/wiki/OK
Post reply on HN