5 ms·
Since we've hit the front page of HN again, I've just released Hammerspoon 0.9.92, which contains a few fixes and some additions, but mostly refactored a signif
by cmsj 5y ago
Since we've hit the front page of HN again, I've just released Hammerspoon 0.9.92, which contains a few fixes and some additions, but mostly refactored a significant amount of internal project structure to allow our build system to be replaced with something that isn't 5 years old and terrible.
As a result, it's possible that something broke which we didn't find in our internal testing. Please file GitHub issues :)
Happy Christmas y'all!
- luckman212 5y agoHammerspoon (and Alfred) are the 2 apps that practically guarantee I'll never leave macOS. Just too damn useful. Thank you
- lycopodiopsida 5y agoThank you very much for your work! I am slowly oscillating between Keyboard Maestro and Hammerspoon, as well as between Alfred and Launchbar, but currently I am again in the Hammerspoon/Launchbar side of the pool :) One side I've noticed Hammesrpoon is a bit difficult to work with is debugging it can be done with logging to the console, but is not very convenient. Are there plans to introduce something more advanced at some point in the future?
- rufugee 5y agoI've used ZeroBrane to debug HS in the past: https://github.com/Hammerspoon/hammerspoon/issues/1268 https://github.com/Hammerspoon/hammerspoon/issues/1268
- lycopodiopsida 5y agoAh, almost, but it seems that ZeroBrane Studio is not arm-ready :( dlopen(/Applications/ZeroBraneStudio.app/Contents/ZeroBraneStudio/bin/clibs53/socket/core.dylib, 0x0006): tried: '/Applications/ZeroBraneStudio.app/Contents/ZeroBraneStudio/bin/clibs53/socket/core.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/lib/core.dylib' (no such file)
- mthoms 5y agoPlease forgive what may be a naive question: Speaking of old and terrible... Are you planning to keep the project in Objective-C long term? Any chance of migrating to Swift? Merry Christmas and thanks for a great project.
- cmsj 5y agoI don’t think that’s a naive question at all, it’s something I’ve been thinking about a lot recently. We have something like 70k-75k lines of ObjC and plain C in Hammerspoon, written at various times over the last 7ish years, with varying architectural styles as we’ve figured out better ways of doing things. I would love to have it all ported to Swift with a single, consistent architecture, but it’s a heck of a lot of work! I’ve been experimenting with some ideas for how the Swift might look, but to really justify all that work I think we’d need to revamp how our user-facing API works, so we’d also be forcing all our users to rewrite their Lua configs. In summary… ¯\_(ツ)_/¯
- mmargerum 5y agoIDK i ported my objC code to swift and didn't see much of a benefit. If anything it was more work because I relied heavily on objC dynamism.
- harryvederci 5y agoDecision tree so you can stop pondering: Does the current situation hinder progress? - Yes: A lot? - Yes: rewrite - No: don't rewrite - No: Don't rewrite
- boffinAudio 5y agoThank you so much for Hammerspoon! It regularly makes my life much, much easier. Only thing I'd wish is for it to be ported to Windows and be 100% compatible with my existing scripts. ;)