🚀 go-pugleaf

Are they also scared of Hungarian notation? I get sick of seeing "my" at the beginning of every variable name in examples, it seems redundant and silly (I'd prefer "o", "obj", "v", etc. if you're going to use the same prefix for everything). But perhaps the "my" prefix introduces the concept of a variable?

I would think the best solution to the "to Dim or not to Dim" question would be:
(1) For advanced discussion, technical documentation, include a VB example, using Option Explicit.
(2) For introductory discussion, bare-bones examples, use VB Script examples.

I think in any substantive document, i.e. documentation, you would definitely want both an Option Explicit VB example and a VB Script example.

Declaring objects in VB helps those of us coming to InDesign from a programming perspective learn the InDesign objects more quickly and gives us a better understanding of the InDesign object model.

Strongly typed VB is a nice middle ground between C++ and VB Script. I would think any company, even a graphic arts company, who maintains a code base for automating InDesign on a Windows platform, would want to use Option Explicit VB over VB Script (or VB without using "Dim"). And certainly for a company doing this VB makes more sense than C++, as it is infinitely easier to find someone to update/maintain VB code than C++.

Graphic artists should think long term: copy the silly "Dim bit" for now and figure it out later. Then their code will scale. The most important skill for a graphic artist starting out scripting is copy and paste.