News for hackers. Stuff that matters.
Re:The logging framework isn't a bottleneck, and other lies ... by orisho on Thursday May 14, 2020 @04:33AM (#23176983)
Render is the term used by many templating languages to denote transforming a template to a result using parameters. So in the case of web apps that use templates, it's the terminology commonly used (you could argue about its correctness, but it is this word). For example, the jinja2 library names the transform function 'render'.
Re:The logging framework isn't a bottleneck, and other lies ... by qubex on Thursday May 14, 2020 @04:43AM (#23177040)
> you could argue about its correctness

Yes, I do. But as you say, it’s in circulation. I guess I dislike it in the same way that I consider ‘literally’ and ‘figuratively’ to be antonyms, but how the former has unfortunately come to be considered a synonym of the latter, which basically hobbles the language permanently.

Re:The logging framework isn't a bottleneck, and other lies ... by theelous3 on Thursday May 14, 2020 @04:59AM (#23177173)
It really doesn't "hobble" language. In all the time since the muddying of the word literally, I've yet to come across a use of it that can't be inferred contextually. The end result is that now there's even more flavor to language, not that it's hobbled.

People complaining about literally being watered down, literally need to chill. Go read a non-technical book or something and re/learn that language is absolutely unstrict. You can do whatever the hell you want with it and use words in ridiculous ways, and it's all valid. The only thing that matters is communication. If you understand that "I literally died when I saw it come off" and "he literally couldn't fit through the doorway for 20 minutes" have different uses of literally, what's the issue? You want every word to be a reserved keyword?

Re:The logging framework isn't a bottleneck, and other lies ... by qubex on Thursday May 14, 2020 @05:13AM (#23177284)
> I’ve yet to come across a use [...] that can’t be inferred contextually

I literally think that’s impossible.

Re:The logging framework isn't a bottleneck, and other lies ... by theelous3 on Friday May 15, 2020 @01:40PM (#23194964)
So what's hobbled?
Re:The logging framework isn't a bottleneck, and other lies ... by simiones on Thursday May 14, 2020 @04:57AM (#23177160)
Who considers "literally" to be a synonym for "figuratively"? I would venture that almost no one. In fact, it is used exactly for its proper meaning, as a hyperbole.

If I say "I feel so embarrassed I could literally die", I am using literally in its proper sense, but hyperbolically. Just like if I say someone was "a mountain of a man" I am using the proper sense of "mountain", even though the man is not literally a mountain.

Re:The logging framework isn't a bottleneck, and other lies ... by gwd on Thursday May 14, 2020 @06:40AM (#23177862)
> If I say "I feel so embarrassed I could literally die", I am using literally in its proper sense, but hyperbolically.

I'd rather say they were using "literally" as a meaningless intensifier. But here's the thing: We already have loads of intensifiers. But we don't have very many ways of saying, "I'm not speaking hyperbolically, this actually happened."

Think of all the words that, etymologically speaking, should mean "this actually happened", but in fact don't mean anything anymore: really, truly, definitely, and so on. The reason they didn't say "I feel so embarrassed, I really could die" is that "really" has lost its strength from overuse; now they've moved on and are trying to do the same thing to "literally".

"Literally" is my (figurative) line in the sand: This far and no farther. Language is defined by its speakers: I'm an English speaker, and so I get to vote on how the language is used. As such, I will continue to make fun of people who say "I could literally die" as long as it is possible, and I encourage everyone to do the same.

Re:The logging framework isn't a bottleneck, and other lies ... by PeterisP on Thursday May 14, 2020 @09:36AM (#23179296)
The figurative meaning is now considered one of the major senses of the word "literally" because it's so widely used - see https://www.oxfordlearnersdictionaries.com/definition/englis... sense #3, the same for other major dictionaries now.
Re:The logging framework isn't a bottleneck, and other lies ... by gwd on Thursday May 14, 2020 @10:00AM (#23179584)
Dictionaries are descriptive, not prescriptive. You have a vote -- use it wisely.
Re:The logging framework isn't a bottleneck, and other lies ... by PeterisP on Thursday May 14, 2020 @06:46PM (#23186519)
Dictionaries are descriptive but conservative - so by the time a change gets included in major dictionaries, it's a sign that the language shift has definitely happened by now and it would be considered futile to try and reverse it because it's already ingrained, it's here to stay.
Re:The logging framework isn't a bottleneck, and other lies ... by perl4ever on Thursday May 14, 2020 @08:31AM (#23178640)
I question whether "I could literally die" is precisely the same thing as "I literally could die".

That is, maybe the former means "I could (figuratively) literally die", while the latter means "I literally (not figuratively) could die".

Re:The logging framework isn't a bottleneck, and other lies ... by qubex on Thursday May 14, 2020 @10:55AM (#23180280)
I think we’re getting a bit distracted here by the fact that the frequently used “I literally died [of embarrassment]” is obviously figurative because nobody would be able to use the verb “to die” in the first person in the past tense.

When you get to thinks like “She literally died” it becomes murkier. “I could literally die if I ate shrimp” is murkier still.

This is one of the many reasons I’d like a firm firewall between ‘figuratively’ and ‘literally’. It seems I’m constantly besieged by the “language evolves, deal with it” crowd, but what they don’t get is that it’s all fine and well when language evolves in such a way to become more precise (perhaps by adding terms that distinguish between things that were previously lumped together, such as ‘dumbphone’ and ‘smartphone’ splitting from ‘cellphone’, itself a portmanteau of ‘cellular’ and ‘telephone’, to distinguish it from a fixed line) or to make meanings quicker to convey in conversation (by abridging the latter to ‘convo’, for example), but the ‘figurative’ versus ‘literal’ debate is very different, because it’s one of those relatively few instances that add ambiguity, making meanings (at least potentially) harder to convey.

Re:The logging framework isn't a bottleneck, and other lies ... by gwd on Thursday May 14, 2020 @09:58AM (#23179560)
"I could literally die if I eat shrimp." "I could literally die of this disease." Those sound like "this actually happened" to me.

"I can't believe I did that in front of all those people -- I literally could die of embarrassment." "I can't believe I did that in front of all those people -- I could literally die of embarrassment". Those both sound like normal "meaningless emphasis" usages of the word 'literally'.

Re:The logging framework isn't a bottleneck, and other lies ... by theelous3 on Friday May 15, 2020 @01:47PM (#23195035)
> I'd rather say they were using "literally" as a meaningless intensifier

Strange how something "meaningless" can simultaneously be an intensifier.

Re:The logging framework isn't a bottleneck, and other lies ... by orisho on Thursday May 14, 2020 @04:52AM (#23177118)
Yes, that one is definitely very unfortunate :(
Re:The logging framework isn't a bottleneck, and other lies ... by qubex on Thursday May 14, 2020 @04:54AM (#23177140)
I literally hate it. ;)
Re:The logging framework isn't a bottleneck, and other lies ... by filleduchaos on Thursday May 14, 2020 @09:07AM (#23178988)
I take the completely opposite stance: things like the dual usage of "literally" are less symptoms of a hobbled language and more symptoms of hobbled language skills in those that complain about them.

And I mean that literally; rigid educational systems have stamped the fluidity of language out of far too many people.

Re:The logging framework isn't a bottleneck, and other lies ... by qubex on Thursday May 14, 2020 @10:46AM (#23180175)
Then you’re entirely willing to concede that “Quack quack quack, quack quack, quack quack. Quack quack quack quack.” is entirely intelligible because you can easily ascribe multiple meanings to various instances of ‘quack’ so that it makes sense?

The point being that there’s definitely a threshold beyond which ambiguity of meaning makes parsing a sentence and resolving its meaning impossible. The more specific (and distinguishable) terms are, the less risk there is of a misunderstanding. This is Information Theory 101.