2 ms·
This post fails to speak to me on two fronts: * The `nix` crate is a cornerstone of the Rust development ecosystem: if you do anything that requires POSIX or v
by woodruffw 5y ago
This post fails to speak to me on two fronts:
* The `nix` crate is a cornerstone of the Rust development ecosystem: if you do anything that requires POSIX or various *nix-specific APIs beyond those wrapped by the standard library, then `nix` most likely provides a high-level and safe wrapper for them. Perfectionism is a virtue in this context, one that keeps large parts of the Rust ecosystem from accidentally consuming buggy code. The author unfortunately chose a particularly messy and bug-prone corner of the POSIX APIs to wrap, and ran into a correspondingly intensive review process. I've merged simpler wrappers[1][2] with no fuss.
* Alacritty seems to work just fine. I switched to it about two months ago, after using nothing but (heavily customized) rxvt-unicode for a decade. Maybe it's because I don't use ligatures or images in my terminals (I thought we were talking about non-"toy" functionality!), but I haven't found myself wanting for anything beyond what Alacritty already does. And the scrollback seems to work nicely. To summarize: where's the tragedy?
[1]: https://github.com/nix-rust/nix/pull/1342 https://github.com/nix-rust/nix/pull/1342
[2]: https://github.com/nix-rust/nix/pull/1331 https://github.com/nix-rust/nix/pull/1331