I wanted to build my own window manager at some point, but was quickly scared away by the lack of a proper API on MacOS. You basically need to hack your way around it by using the accessibility API instead. I see this project uses Objective C bindings and the accessibility API and am wondering how easy it was to debug, write features and what kind of tooling was used for this.
The Accessibility framework is not what I would call a "hack" personally. It was quite well thought out and fully featured
I've spent the last month working on something similar in Rust with various macOS framework bindings and it's not really that scary
You don't really need anything other than a Rust dev env, rust-analyzer and a browser window with the Apple docs website and the objc2 crate docs.rs site open - no special XCode craziness required
Any vacation or trip planned soon? An alibi you were away from home could prove you’re not the source of the noise.
We recently had a very similar situation. It makes you feel quite powerless and frustrated, I hope you guys figure it out soon. Mediation is key in a situation like this, so it’s nice the building owner is already involved. We tried being proactive and showed good will to our downstairs neighbor but unfortunately they kept complaining. The landlord had ensured them, it wasn’t us. In the end it turned out to be coming from somewhere else. Or at least that’s what they started believing.
heh I notice I really don’t care what any of the terminal emulators provide in terms (get it) of functionality. iTerm2 now has “AI”. What?
As long as I have my good ol trusty tmux setup I’m good. Since the multiplexer _is_ the middleman it has become the perfect place to implement functionality which would otherwise be emulator specific.
For me kitty’s main upside is its configuration dotfile that can be version controlled. I used iTerm2 for years, but moving around multiple computers makes it harder.
Oof, Pulumi here. A module was wrapping a Terraform module which wraps a REST client which wraps the provider’s API. Errors only came forward during a `pulumi up` instead of being caught during a `preview`. Fun times digging through those multiple layers of abstractions
Heh! I just started using keycloak y'day in combination with oauth2-proxy to give me a way of completely delegating authentication. This way I don't have to worry about auth _in_ any of my apps. Really nice experience so far and fantastic documentation.
I recently naturally grew into a management role due to seniority and churn. I cannot wait to get back to becoming an IC again. All these meeting are tiring and unrewarding. Growing team members is pretty rewarding, but I don't have to be a manager for that.
Disagree with OP on giving up control of the code base. You are still responsible for the quality the team delivers and in many companies your seniority will mean you'll still code review. You just no longer have the time to actively steer. Not a nice position IMO
Just. Wow. This has piqued my interest, is there any background information as to why this happened (so often)? There must have been underlying tentions, wondering what those were, but can imagine it's just lost to history
There's some important context that's also not covered by the Wikipedia article: the Black Death swept through Europe from 1347–1350. England's population declined by almost half and would not recover to the same level until the 1600s. As we've seen with covid, but just as a shadow, the population decline led to a huge labor shortage and high inflation. So, 1355 wasn't a happy time.
Tried Komorebi while running Windows and liked it a lot! Got too annoyed with Windows in general and went back to PopOS with tiling enabled. Would love to see PopOS’ intuitive window swapping/stacking in Komorebi one day
