An appropriate amount of work to slap an MIT license on somebody else's work
2026-07-02 15:24 UTC
Replies (6)
-
@KindaABigDyl@programming.dev 2026-07-02 16:28
Are they using any original GNU coreutils code as reference? My understanding is nothing is 1:1. They’re trying to build, from the ground up, a totally new codebase that has the same user-facing functionality but under the hood is idomatic Rust code (so nothing like the GNU C code) They are recreating something that matches behavior not using licensed GPL code. Which is the same way the GNU coreutils were a recreation of the proprietary Unix tools in an effort to provide open source alternatives. Like you wouldn’t say “An appropriate amount of work to slap a GPL license on somebody else’s work” in reference to GNU recreating the Unix tools, so why say it here?
-
@onlinepersona@programming.dev 2026-07-02 17:53
Can somebody explain why they are using libc in the first place?
-
@fruitcantfly@programming.dev 2026-07-02 22:40
I can’t believe that Rust developers would call POSIX functions to interact with the operating system! The audacity!
-
@savvywolf@pawb.social 2026-07-03 00:49
This “someone else” being… A C API header which can’t be copyrighted/copylefted anyway?
-
@cornishon@lemmygrad.ml 2026-07-03 10:43
What do you think all the command line utils named after linux syscalls are doing if not calling the syscall for you?
-
@somegeek@programming.dev 2026-07-03 16:49
Fuck this rust coreutils projects. I’m sure it’s google, meta and some other shits behind it. Otherwise, the creators are just too fucking dumb for licensing their project under MIT.