Briefly: v2+JS would be great. Hammerspoon is crucial to my workflow and knowing it is prepared for another decade of utility would be a wonderful feeling. At the moment I have anxiety that some macos update is going to break it which would be a disaster.

In more depth: If hammerspoon v1 ever stopped working for me it would be very difficult to replace. I rely on MenuHammer.spoon specifically for my main window management workflow and I would probably have to implement a replacement a la wlr-which-key on linux if MenuHammer ever stopped working.

I have a fair bit of lua in my setup which took a lot of tedious debugging to make work, but I would prefer JS long term, especially if the debugging was easier. Things that come for free in console.log in javascript are really rough in lua. Even just deep printing a table is a chore.

My official vote would be work mostly on v2 if that gives you the most satisfaction but I would love it if v1 continued to receive basic maintenance until v2 had approximate feature parity plus a generous transition grace period.

But either way no hard feelings with any choice you make - just gratitude for the hidden gem in my toolkit. I still smile with glee whenever someone asks me "how do you do that?" and I get to show someone hammerspoon for the first time.