A salamander. I see what you did there.

For sure. If Trump’s raving about you, you must be doing something right.

I’m a “completionist” sort of person, so I’d start at the beginning. Not saying I recommend doing so. It’s just a quirk of my psychology.

I upvoted this before I saw what community it was in. Now I wish I could upvote twice.

Oh look what instance this was posted on.

Disney is no stranger to hypocracy of that sort. Look at them making their billions off of the public domain (Snow White, Cinderella, Aladin, The Little Mermaid, need I go on?) while lobbying heavily for longer copyright terms to keep works they made from being similarly adapted.

Nah, that’s an organizer. You’re thinking of the type of aircraft that flies by flapping its wings.

What’s the deal with moths? Am I out of the loop and it’s just the new beans/stroganoff/poop-holding?

Oh, no idea.

English.

Yeah, I think “a slice of bread” is a lot more common than “a bread slice”. Not to say I haven’t ever heard “a bread slice” used. I’m sure I have at least a few times. It would be pretty rare, however.

Though, I’m not sure “a pizza slice” is all that much more common. Maybe there are regions where it’s very common? Or maybe it’s more common in certain contexts? Like maybe sell-by-the-slice pizza places might tend to refer to “a pizza slice” rather than “a slice of pizza” when talking with coworkers? (That said, I’d imagine they’d just shorten it further to “a slice” since the “pizza” part would tend to be obvious in that case.)

Also, @eager_eagle@lemmy.world mentioned “water bottle”. I think if I hear “a water bottle” rather than “a bottle of water”, I’m probably going to assume it may or may not be an empty bottle intended for water rather than a bottle filled with water as “a bottle of water” would imply.

Way off the topic of programming, but linguistics is fascinating too!

The Go programming language documentation makes a big deal about how it “reads from left to right.” Like, if you were describing the program in English, the elements of the Go program go in the same order as they would in English.

I say this as someone who likes Go as a language and writes more of it than any other language: I honestly don’t entirely follow. One example they give is how you specify a type that’s a “slice” (think “list” or “array” or whatever from other languages) of some other type. For instance a “slice of strings” would be written []string. The [] on the left means it’s a slice type. And string on the right specifies what it’s a slice of.

But does it really make less sense to say “a string slice”?

In Go, the type always comes after the variable name. A declaration might look like:

var a string

Similarly in function declarations:

func bob(a string, b int, c float64) []string { ... }

Anyway, I guess all that to say I don’t mind the Go style, but I don’t fully understand the point of it being the way it is, and wouldn’t mind if it was the other way around either.

Edit: Oh, I might add that my brain will never use the term “a slice of bytes” for []byte. That will forever be “a byte slice” to me. I simply have no choice in the matter. Somehow my brain is much more ok with “a slice of strings”, though.

My grandmother was similarly god-like at the NES Dr. Mario.

No, that’s a U.S. state in the north-west of the contiguous 48.

DALLE LLaMA

Go:

So they won intentionally. ;)

Failing? I call that a win.

“Oh, am I supposed to kiss it?”

describing IntelliJ as “good”.

Shots fired back. 😈