AHK++ will go into maintenance mode on January 1, 2027 #686
mark-wiemer
announced in
Announcements
Replies: 2 comments 1 reply
-
|
End of an era. Good luck for the future. 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Oh dang! You too! :D |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, it's 2025-12-30 and I haven't written a PR for AHK++ in a lot of months. I am healthier now, but very busy, and using Linux full time. As such, there hasn't been any reason for me to use AHK++, and it's been hard to test potential fixes. I do plan to upgrade my PC and get a Windows VM setup on my new machine (I've already set aside a budget and experimented with QEMU), but I don't see Windows ever becoming my main operating system again.
That said, I appreciate that this extension remains the only comprehensive v1 + v2 VS Code extension (that I know of), and I will spend some time in 2026 reviewing the open issues and prioritizing high ROI ones when I have time. I still love coding for VS Code extensions, formatters, and lexers, so rest assured I'm also doing this out of passion, not just a sense of obligation. I've decided a 1-year notice should be sufficient for folks to plan forks or other migration strategies.
In 2027, I'll pause any new feature work, and only work on critical security issues or weird major bugs that new versions of VS Code (or other supported IDEs) might introduce. I'll still monitor notifications and respond as needed.
See also the the same announcement on AHK Community. Thanks as always for all your patience and support, this continues to be a very fun project to work on (or at least, think about!)
2026-01-14: Clarify that discussion on both GitHub and AHK Community are OK
Beta Was this translation helpful? Give feedback.
All reactions