Conversation

Totally agree with this, case sensitivity does not add a lot apart from errors. Also note that some languages (Arabic, for example) do not have uppercase letters! So the whole idea of "case sensitive" to some people is new (and thus can make learning to program a lot harder)

Quote Tweet

Jeffrey Snover

@jsnover

· Mar 22

Unpopular but correct opinion: Case sensitivity in programming languages provides minimal real utility while exponentially increasing the potential for errors. It was a reasonable call when most variables where 1-3 characters but that was many decades ago. Not today. twitter.com/buhakmeh/statu…

Quil (キュー)

@robotlolita

Mar 23

A handful of languages also use casing for different semantics, so the potential for confusion is even greater there. Like Erlang and Prolog use Uppercase identifiers to mean a variable name, lowercase to mean an atom. The visual distinction is very useful once you learn it, tho.

Replying to

and

Yeah. I've been using casing by convention for terms vs. types - eg. `a : A`. It's nifty at first, but I've found it gets pretty difficult to distinguish them when talking about code verbally, which is pretty important especially for learning/teaching! 😬

8:14 AM · Mar 23, 2022Twitter Web App

Replying to

and

I have a section about this in Crochet's documentation because spelling ambiguities are part of the threat model (crochet.qteati.me/docs/reference), but the examples there are all in Japanese's use of four different "alphabets" to write the same thing. Still unsure how to deal with it.

Brendan Zabarauskas

@brendanzab

Mar 23

Cool example! Hadn't thought of hiragana vs. katakana vs. kanji (curious what the fourth is?).

Show replies

Replying to

and

Linguistically I think the thing I am running into is that English often overloads objects and classes. Like "the cat is curled up in the sun" or "the cat named Bobbins". Not sure if there is a technical name for this, and if it appears in other languages.