therubyracer VS hawck

I use both OSX and Linux extensively. I had the choice to go either way for my work computer and I chose OSX (intel chip).

A couple of days ago I wanted to use a Ruby gem ( https://github.com/rubyjs/therubyracer ) for some random project. To install the library (compile native bindings), OSX wanted me to download an install 12 GB of crap (full XCode, it didn't work with the command line tools)... In linux it was just a matter of downloading and installing the gem (100MB at most). That's crazy.

What I dislike more and more about OSX is how they have been aggresive against developers and technical people in the last years (like, why do I have to jump through hoops to modify my /usr/lib folder with SUDO/root? I AM ROOT ASSHOLE OS, LET ME DO WHATEVER I WANT TO MY COMPUTER.

But other than that, it's OK.

That is actually very smart and helpful, thanks! :) My only gripe with autokey is that it's the only thing holding me back from wayland. Hawck is supposed to work with wayland but I never got it to work, was a while ago I though

https://github.com/snyball/Hawck

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Hawck?

>Creating a "standardized experience" like Windows usually means that configurability goes right out the window. It's how you get abominations like dconf or the GNOME music player

I don't understand how you connected these dots and I'd suggest against calling things abominations. You don't have to use dconf or the GNOME music player, those aren't standardized. If someone does like them I think they're perfectly fine, they do exactly what they're advertised to do. It's also fine if you don't like them, they're just two options from the many configuration databases and media players that you can choose from.

>But why shouldn't I be able to run xbindkeys or sxhkd or whatever hotkey dameon I want?

In some ways you actually can but it depends on the hotkey daemon and how it's implemented. The reason for that is technical, those are implemented with X grabs which have a number of usability and security issues. There are a few key rebinding daemons that use evdev directly so they work with Wayland:

https://github.com/samvel1024/kbct

https://github.com/snyball/Hawck

But these also do have similar security issues to X key grabs, in that they effectively operate as keyloggers. If you're looking for an API that works purely within Wayland and lets unprivileged clients request key rebinding, that doesn't exist yet. Somebody would need to specify what that API looks like and figure out a good way to make it secure. What would the end goal of the API be, and how could the system (and by extension, the user) tell the difference between a legitimate hotkey daemon and a malicious keylogger? And would it actually be any better than the approach of snooping evdev? I don't know the answer to these questions but you may have more experience with this than I do.