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!
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!
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.
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… ¯\_(ツ)_/¯
Does the current situation hinder progress?
- Yes: A lot?
- Yes: rewrite
- No: don't rewrite
- No: Don't rewriteOne 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?
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)
Only thing I'd wish is for it to be ported to Windows and be 100% compatible with my existing scripts. ;)