Linux

11930 readers

436 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

cpx Introduced as a Faster, Modern Replacement for Linux cp (linuxiac.com)

submitted 4 days ago* (last edited 4 days ago) by cm0002@digipres.cafe to c/linux@programming.dev

45 comments fedilink hide all child comments

As we all know, file copying on Linux has long relied on the classic cp command, which remains reliable but offers little feedback and limited control over long or complex operations.

To address this, a promising new Rust-based command-line tool called cpx emerge, designed as an alternative rather than a replacement, that approaches the same task with a focus on performance, visibility, and configurability.

It targets scenarios where large directory trees, interrupted transfers, or the need for detailed progress reporting make standard tools less convenient to use. The project is currently Linux-only and leverages modern kernel features to improve copy throughput and reliability.

you are viewing a single comment's thread
view the rest of the comments

[–] pinball_wizard@lemmy.zip 6 points 3 days ago* (last edited 3 days ago) (1 children)

What's wrong with the MIT License?

Good question.

Failure to copyleft contributes to "embrace extent extinguish", which many of us feel is a constant threat to the ecosystem of our favorite tools.

For example, Google can make a better expanded XMPP client, and keep extending it until the open XMPP clients are no longer compatible - drawing most of the userbase away from the free open ecosystem. (Source: I fell for that shit, and I lost track of dear friends who I used to regularly chat with over XMPP.)

MIT license also risks security patches being written by big corporations for their own use, and not getting contributed back to the commons.

I'm not really sure these risks particularly apply for a 'cp' variant, honestly.

But I'm onboard now with not making anything unnecessarily MIT license.

[–] brian@programming.dev 1 points 2 days ago

Google could have done that from the spec though. Google is doing that with chromium despite the source being entirely available

even agpl wouldn't protect this tool in most cases if a company didn't want to contribute back, since it's probably just used in server side scripts and such. also companies aren't required to upstream stuff, just make source available, which means hard to discover ftp site with a pile of code.

sure something more copyleft is better for large, more commercial projects, but this in particular probably gets more patches from the extra use in the rust community from MIT than they would forcing companies to open source changes