Some functions also don’t have any parentheses, like field access or infix operators.

You call things the way they were defined. Problem solved.

I'm kinda confused, because this is the second time now where your attempt at making a counter argument is actively supporting my point. Is this intentional at your part?

We could follow this line of thinking further ...

No we don't. If your point relies on Turing-tarpitting the whole discussion ... then you have no point.

Thankfully, registration fees do not differ by length of the domain. (As it should be.)

It cost a larger 3 digit amount of currency to buy it, though. (Which was fine for me.)

Packages are usually provided by distribution packagers, not by the developers of the code itself.

This submission reminded me that I also had some articles on this topic that people may find interesting.

That's still a workaround to try and keep a completely artificial distinction alive.

Even if I didn't need [] for types, I still wouldn't want "some functions use (), some functions use []" as a language rule.

Oh, good idea ... any preference on the first? :-)

I have some articles on naming specific areas of program code that people might find helpful:

• Naming language keywords
• Naming value creation operations
• Naming value conversion operations
• Naming operations on Options and Results
• Naming lookup operations
• Naming operations on Streams

Happily using it for presentation slides.

If you read more than just the headings, you'd find out that your objections have been addressed in the article. ;-)

What blog?

To spell it out for you, very slowly: Casing is locale-sensitive.

You cannot determine whether file A and file B have the same case without taking the language the filename was written in into account.

Which means you need to somehow attach the locale to every file (name). Your browser could implement something to add that (semi-)automatically, but if grandma is creating a file from scratch, there is only so much you can do.

I hope this helps you understand why the thing you propose is stupid.

Good catch, that should have been if person in the first line.

It's been a left-over from when syntax looked like this:

  is Person("Alice", _)$person then "{$person.age}"
  is Person("Bob", $age)       then "$age"