152
Permanently Deleted
(reddthat.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Some have better ux, some support more platforms out of the box. I don't find it a good idea trying to replace everything though.
I only tend to replace if all of those are met:
So far, only things I've actually replaced are aliasing
lstoexa/eza, and switched toripgrepfor most of my uses ofgrep.Looks neat, but again, 99% of those utils I've never ever thought "this shit too slow" or "UX sucks". Replacing for the sake of replacing I'm not too keen on.
I know, but coreutils also literally never broke on me as they are. To me, the whole point of coreutils is that they're just... there. I'll leave the decision to change bundled tooling to distro maintainers.
I'll also be perfectly honest: from a developer standpoint, end-users caring about the language a tool was developed with is, in the end, a pretty weird concept to me. Memory safety and cross platform compilation is DX stuff. Nothing tells you as a user that the thing you're using isn't sprinkling
unsafeeverywhere, in the end... The application itself doing what it advertises is what I'd expect most users to care about. Especially for stuff as old and relatively stable as most coreutils.Ah, except Electron. Fuck most Electron apps.
My point was intended to be more generic than just
uutilsthough. Agreed that this specific project looks interesting.And yes, I know the
unsafekeyword is not inherently unsafe to use, but it's also, in practice, one of the few potential footguns of the language, and is easy to abuse and get wrong. It'll raise a few eyebrows in PRs and you'll be expected to have both good reasons and a good test coverage at the very minimum lol. It's a good red flag, if you do end up with runtime memory issues, that it's probably happening in that block, but past this, you're still basically foregoing some safety for convenience. And people fail. Often.