I notice that Red is only case insensitive for the 26:26 unaccented characters.
>> make object! [café: "Coffee" cafÉ: "Scones" Café: "Tea"]
== make object! [
café: "Tea"
cafÉ: "Scones"
]
As is Rebol 2 but not Rebol 3 (or Ren-C)
In terms of my own case insensitivity, I use initial caps for headers (including Rebol []) as it has a formality to it but would balk at having to use said caps in accessing that information anywhere in the script system/script/header/title. The other place I use it in a mixed way is representing HTTP headers: header-proto: make object! [Content-Type: "text/html"]—there are benefits when it comes to forming headers in such a way, but again, would feel icky to access them that way in paths: header-proto/content-type
This may be a parochial opinion, but I'd be fine with the 26:26 compromise.
As a side note, was just futzing with some JS code that capitalized its camel-cased class names and did not for it's derivatives.
class GreenThing {...}
greenThing = new GreenThing(...)
Whatever funkiness currently exists with associating binding with cased represention, it is not as bad as this.