At some point Apple decided to change Applescript Editor with a generic substitution which isn’t correct. AS Editor would fit better as it’s shorter and not generic.
Maybe it’s just an aesthetic reason to use a variable instead to use a direct call :lol:
Backward compatibility seems no more that easy this days.
I’m not sure if the Applescript Editor was better… In its newer versions - (yose and cap) the compile command causes the document to lose the insertion point and jumps for 2 seconds around like a crazy horse, let’s say from line 100 to line 80 or so. Wasn’t the case in older versions. This happens especially by very long scripts
Maybe this is the time to trash the Script Editor for good.
I’m also very tired of the caveman debugging: Script Debugger or Swift looks less outdated as sad this conclusion is about the vanilla Applescript editor that made us very happy
For backward compatibility Script Editor responds to old app names just fine. No reason to use fancy code there.
AppleScript becomes more strong with each version, from my experience that’s a good thing. An scripting language that is more consistent than randomly choose whatever it likes when on a crossroad is not the way to go. On MS we call them funny quirks but in reality it just allows bad written code that is doomed to fail in some situations.
Keep in mind that SD doesn’t make you a better coder on any level.