I’m greatly saddened to hear the news, but I can understand the reasoning behind the decision. The writing is on the wall for AppleScript & automation in general on the Mac. Script Debugger’s EOL is an absolutely devastating loss for AppleScripters everywhere.
Thank you both for all your contributions & support over the years! Wish you the best with your future endeavours.
Well hell, I was just getting comfortable. It’s like the really good in life always leaves too soon.
Thank you for all you’ve contributed in the short time we’ve been together and not taking it all with you. 
Thank you guys for all the work you have done. Thank you also for the end-of-product calendar; this is really nice to do. I wish you both great things going forward.
The journey in life and the experience from the past could set the path to imagination what we could do in the future. The hard part is not to do what we have learn its to do things nobody else have done. That was my feeling when I decided to stop using AppleScript and leaving MacScripter.net. I like to thank Mark for his effort to running the only forums that still are dedicated to AppleScript or Scripting on macOS platform for all years. I like to thank again Shane Stanley for his kindness and effort to share his knowledge in AppleScriptObjC. It become a easy path to learn how Objective-C framework was working it also set the path to do the same things in PyObjC. I do not think I would have read Apple’s API so much I have done without AppleScript that started it all for me.
I was not directly a Script Debugger user, I like to do it that hard way (no shortcuts) 
but I understand that many people use it when they need something better to debug the code.
Mark and Shane have a great journey to fill yours imagination.
Happy New Year 2025
So Long, and Thanks for All the Fish
ScriptDebugger is the primary reason I continue to use AppleScript for automation projects. Such a great development environment—but that is only half the story. Mark provided such excellent support for so many years. That was/is what is so great about small developers. The ideal.
With Shane’s help he continued to do this for years—a model for everyone. I also want forget my correspondence with Gerry, contributions from Matt, and others. Thanks so much for making my life easier for so many years. I’m sure I will still be using SD into the next decade.
I’m so sorry to hear this news, but so grateful to Mark and Shane, as well as Ray and many others who have helped me so much over the years. I shudder to think about trying to develop any script with any complexity without the use of Script Debugger. Thankfully, I am now also retired, so any scripting I do is mostly for my own enjoyment!
Sorry to read this news!
When I decided yesterday to finally learn AS enough to accomplish relatively simple publishing and design tasks in InDesign and Illustrator, I didn’t know of this announcement!
My decision was made because I need to place dozens of multipage-PDF files into an InDesign document and do some resizing and repositioning and object styling to each PDF page image.
I could do it the laborious way and be finished in a day, but the idea of doing it this way is painful to me when I know this is a trivial task for an AS routine or set of routines. Given Adobe InDesign provides a start with the Multipage PDF import script I thought I have to try (hours later I’m wondering why I fooled myself again to think this would be easy).
Given JS is a language I loath and the sample code from Adobe is verbose when c.f. their AS code I’m choosing AS… and also b/c this excellent tool in SD exists. Beats figurine out Visual Code Studio and JS the thousands of idiosyncrasies for scripting macOS apps.
I didn’t realise Script Debugger was retiring from a marathon innings and setting an MCG-record-score (cricket jargon for those not from Melbourne or the Commonwealth nations — they all play cricket a lot) when I made this decision to finally pony up and learn enough AS to be almost dangerous. Why do I keep choosing “dead” coding languages?* — I was never interested in Latin or Classical Greek!
Hopefully this community will get me over the humps b/c sure as sh!t ChatGTP is worse at writing AS (and JS for macOS application scripting) than I am, I just subscripted to a paid plan because a free ChatGTP session is never long enough to get the bugs out of its terribly randomly generated code. I have to coach it extensively. Now I’ll be patient and ask questions here, even if it makes me look dumb as all heck 
Thanks to Mark, Shane (a fellow Melbournian!) and others, for all the effort that went into making the Script Debugger tool and community. I’ve used the trial version more a few times over the decades to do little bit of macOS/DTP tasks — more on that in my profile but I had to cut it short to fit in the 3,000 character cap
SD is a really sweet tool which is partly why I decided to bit the bullet and try to learn enough AS to be almost a bit dangerous!
Mark and Shane,
I can’t say how much your commitment has helped me.
Thanking you a thousand times is not enough.
Be happy and healthy!