kinto VS nixpkgs

If you like macOS keyboard shortcuts, I recommend you checkout Kinto go Windows and Linux. On Windows, Kinto used AHK

https://kinto.sh

However, at least when I set it up Kinto did not provide switching windows I’m this fashion. Here is the script I use.

```

    ; BRING FORWARD ALL WINDOWS OF THE CURRENT APPLICATION

The project was based on another project that's been around for a few years called Kinto, by Ben Reaves, which notably also has a Windows version (https://kinto.sh) using AutoHotkey. But has no Wayland support (at this time) in its Linux version.

Toshy is based on Kinto.sh, by Ben Reaves (https://kinto.sh or https://github.com/rbreaves/kinto). Kinto is basically an extensive keymapper config that not only shifts modifier keys appropriately for different keyboard types, but has full keymaps for a number of different apps like VSCode. My variant of Kinto adds some features and utilities for managing the services that make it work, and tools like a script to change the function keys mode of any keyboard that uses hid_apple. That means MacBook keyboards mostly, but also some non-Apple keyboards with media keys apparently use that driver module.

I don’t know if you can activate it via a keyboard shortcut, but I use Kinto.sh to swap keys on my MacBooks.

Hello, there's an open issue about this in their repo: https://github.com/rbreaves/kinto/issues/772

There is a setting in keyboard preferences for that.However if you can get yourself used to macOS shortcuts I highly recommend doing so as they seem to be superior especially if you are a programmer and use the terminal a lot, as on macOS you can simply use Command+C to copy from a terminal and Ctrl+C still works for sending SIGINT. Also Command+, will open preferences for almost every application on macOS. Shortcuts on macOS are very consistent across many apps unlike on Linux or Windows. After you get your Linux laptop back you can continue using these shortcuts thanks to a tool called kinto.sh.

Tangential: I'm currently looking for a way to map Mac-style shortcuts on Linux (e. g. Meta + C/V for copy / paste). The only thing I know is https://kinto.sh/, but it looks a bit too janky to my taste. Any other ideas?

And nothing about installing my https://kinto.sh app?

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...