Why "Me."?

NauticalGent

Ignore List Poster Boy
Local time
Yesterday, 20:14
Joined
Apr 27, 2015
Messages
6,712
I was putzin' with ChatGPT and asked her (don't judge me!) what a word (COLSETVERSION) in a connection string meant. She replied with ease so I challenged her to another word in VBA we all use and asked her why MS settled on this word in particular: "Me."

Her answer:
That’s an excellent and intriguing question! The choice of Me as a keyword in Access VBA (and in other VBA environments like Excel or Word) may seem a bit arbitrary at first glance, but it’s rooted in both historical and conceptual reasons influenced by object-oriented programming (OOP) conventions.

Why "Me"? The Rationale​

  1. OOP and Self-Referential Keywords:
    The Me keyword in VBA is conceptually similar to this in C-like languages (e.g., C++, C#, and Java) or self in Python. It provides a way for an object (in this case, a form, report, or class module) to reference itself.

    Microsoft likely chose Me because:
    • It is intuitive in conversational English—"Me" refers to oneself, just as the object refers to itself in code.
    • It’s short and easy to type, a practical consideration for programmers writing repetitive code.
    • It aligns with natural language programming design goals that were popular at the time VBA was developed (early 1990s), aiming to make coding feel more accessible to non-developers or power users working with Office products.
  2. Historical and Visual Basic Legacy:
    VBA (Visual Basic for Applications) evolved from earlier versions of Visual Basic, where simplicity and ease of learning were core design goals. Microsoft has historically focused on creating user-friendly development environments. The choice of Me reflects this focus, as it resonates with non-programmers who may use VBA to enhance Office applications. Unlike more abstract terms like this or self, Me is immediately understandable in plain language, fitting the approachable nature of the language.
  3. Consistency Across the Office Ecosystem:
    Using Me across all Office applications (Access, Excel, Word, etc.) helped maintain a consistent programming model, making it easier for developers to move between these environments without having to learn different self-referential terms.

Why Not "This" or "Self"?​

  • "This" is used in C-derived languages, reflecting the need for distinguishing context in strongly object-oriented programming.
  • "Self" is common in languages with a more academic or purist approach to OOP (e.g., Smalltalk, Python).
In contrast, "Me" in VBA emphasizes usability and readability over strict adherence to formal programming norms, aligning better with Microsoft's audience for Office automation.

Conclusion​

Microsoft likely settled on Me for its approachability, consistency, and plain-language simplicity. It reflects their user-centric design philosophy in the early days of VBA’s development. It's short, easy to understand, and fits the metaphor of referring to "myself" in code.

So, in essence, the decision was a blend of usability, readability, and linguistic intuition, making it a hallmark of VBA's user-friendly design!
 
Lets keep this PG, there AB...!
 
Here's what my AI would say, assuming I ever made one, which I won't:

"It's not that deep bro." 😂
 
And, of course, there is Goedel's Completeness Theorem, which says languages can be complete or correct, but not both. Goedel might say that languages containing Me, This, or Self are all incorrect because the ability to self-reference means the language is complete. And that is sort of like Heisenberg's Uncertainty principle that lets you know precise position or precise momentum but never both at the same time.
 
And, of course, there is Goedel's Completeness Theorem, which says languages can be complete or correct, but not both. Goedel might say that languages containing Me, This, or Self are all incorrect because the ability to self-reference means the language is complete. And that is sort of like Heisenberg's Uncertainty principle that lets you know precise position or precise momentum but never both at the same time.
One thing I know is that uncertainty is absolutely certain.
 
Then, of course, there is the parents' answer:

Why me?

Because!
 
Love english-like languages, the more they flow like common sense english the better.
And dislike the stupid stuff like python's ELIF, which appears to have been thought of as funny in the eyes of the creator, but is decidedly not funny.
 
I was putzin' with ChatGPT and asked her (don't judge me!) what a word (COLSETVERSION) in a connection string meant. She replied with ease so I challenged her to another word in VBA we all use and asked her why MS settled on this word in particular: "Me."

Her answer:
That’s an excellent and intriguing question! The choice of Me as a keyword in Access VBA (and in other VBA environments like Excel or Word) may seem a bit arbitrary at first glance, but it’s rooted in both historical and conceptual reasons influenced by object-oriented programming (OOP) conventions.

Why "Me"? The Rationale​

  1. OOP and Self-Referential Keywords:
    The Me keyword in VBA is conceptually similar to this in C-like languages (e.g., C++, C#, and Java) or self in Python. It provides a way for an object (in this case, a form, report, or class module) to reference itself.

    Microsoft likely chose Me because:
    • It is intuitive in conversational English—"Me" refers to oneself, just as the object refers to itself in code.
    • It’s short and easy to type, a practical consideration for programmers writing repetitive code.
    • It aligns with natural language programming design goals that were popular at the time VBA was developed (early 1990s), aiming to make coding feel more accessible to non-developers or power users working with Office products.
  2. Historical and Visual Basic Legacy:
    VBA (Visual Basic for Applications) evolved from earlier versions of Visual Basic, where simplicity and ease of learning were core design goals. Microsoft has historically focused on creating user-friendly development environments. The choice of Me reflects this focus, as it resonates with non-programmers who may use VBA to enhance Office applications. Unlike more abstract terms like this or self, Me is immediately understandable in plain language, fitting the approachable nature of the language.
  3. Consistency Across the Office Ecosystem:
    Using Me across all Office applications (Access, Excel, Word, etc.) helped maintain a consistent programming model, making it easier for developers to move between these environments without having to learn different self-referential terms.

Why Not "This" or "Self"?​

  • "This" is used in C-derived languages, reflecting the need for distinguishing context in strongly object-oriented programming.
  • "Self" is common in languages with a more academic or purist approach to OOP (e.g., Smalltalk, Python).
In contrast, "Me" in VBA emphasizes usability and readability over strict adherence to formal programming norms, aligning better with Microsoft's audience for Office automation.

Conclusion​

Microsoft likely settled on Me for its approachability, consistency, and plain-language simplicity. It reflects their user-centric design philosophy in the early days of VBA’s development. It's short, easy to understand, and fits the metaphor of referring to "myself" in code.

So, in essence, the decision was a blend of usability, readability, and linguistic intuition, making it a hallmark of VBA's user-friendly design!
Sometimes I almost think ChatGPT strives for 1-page answers. Not a half page, not a page and a half, but one page.
 
And dislike the stupid stuff like python's ELIF, which appears to have been thought of as funny in the eyes of the creator, but is decidedly not funny.
So true honestly. I like how they named the language after the comedy group but this one was less funny XD
 

Users who are viewing this thread

Back
Top Bottom