I'm a fan of this. My own projects on GitHub have an action[1] which autocloses and autolocks any opened issues until they have been reviewed and accepted by me, and I only consider feature requests from sponsors.
The real miss here is that there isn't a way on GitHub to only allow maintainers to create issues, instead we are left with these subpar workarounds.
1. Set a default label for issues (e.g. “autoclose”)
2. Make your auto closing and locking logic based on that label (eg the label-actions github action)
3. As a maintainer, remember to remove the label when creating an issue!
Not consistently, but there have been a few months this year where I have hit $500 selling individual commercial use licenses for my tiling window manager[1]
The experiment is end-user mediated wealth redistribution from large corporations by leveraging reimbursement mechanisms, and so far I'm content with the results
Took a look at this and it feels like it is implemented using public macOS frameworks so it shouldn't break between macOS updates
My guess is that kAXWindowMovedNotification, kAXWindowResizedNotification, kAXMainWindowChangedNotification etc. are being listened to on the currently focused window using the Accessibility framework, and there is a callback which gets the latest position of the tracked window whenever it is fired, and uses that position as a reference to update the border position
The border window itself is most likely an NSWindow, which is why the tracking of the border with the target window feels quite sluggish
Fwiw I think this is the right approach. The trade-off between stability across OS updates vs tracking performance is a no-brainer for me - the absolute last thing that I would want is a deluge of bug reports with no other information than "it stopped working" when Apple pushes out an update
As a developer I would interpret that as "try it in the new OS and you will immediately see what is wrong so there is no reason for me to write a tedious and unnecessary message to you".
Very nice idea, thank you for developing it. With an M1 iMac, though the window border lags the position of the window quite a lot if you drag it around, so probably not usable for me.
Some lag is probably going to be unavoidable with a third-party app. The only way to have perfect synchronization of window dragging/resizing and the border is for macOS to implement this as a first-party feature.
It's very sad that none of these Linux DEs expose APIs for customization in anything other than JavaScript - I would love to be able to build on Gnome or KDE with something equivalent to windows-rs or objc2
js is the easiest language to handle safely and securely (due to its origins in the browser, of course), and can even be run fairly efficiently since it is now probably the most optimized language. And most importantly, is probably the most widely known language.
Many megacorps provide value to users. For example Google and Apple are used by maybe 75% of humanity. Google in particular appears to have given back into the ecosystem (often to Google's detriment). It isn't as binary as you make it to be.
hello, can you share the lobsters forum invite with me?
I checked your portfolio and see the socials we used together, I also have X account.
my X: frontendhashira
The real miss here is that there isn't a way on GitHub to only allow maintainers to create issues, instead we are left with these subpar workarounds.
[1]: https://github.com/LGUG2Z/komorebi/blob/master/.github/workf...
reply