News for hackers. Stuff that matters.
Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by zorked on Monday November 06, 2023 @08:54AM (#38162584)
Kinda? Historically there were indeed concerns about reimplementation and copyright. One of the ways that the GNU Project tried to fight claims was to reimplement the tools using dynamically-allocated memory (instead of Unix's traditional fixed-size buffers) to make sure the implementation was sufficiently different. Other ways were making the implementation Posixly correct, adding internationalization or trying to pick different approaches (like using more modern algorithms for sorting). The GNU tools were better, not just direct ports, and that's why it was common to install them in systems like Solaris or HP-UX.
Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by iudqnolq on Monday November 06, 2023 @09:52AM (#38163381)
Arguably writing in Rust will force a similar magnitude difference to those examples. For example, you'll probably replace that modern sorting algorithm with a call to .sort
Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by mustache_kimono on Monday November 06, 2023 @12:14PM (#38165386)
> Kinda? Historically there were indeed concerns about reimplementation and copyright.

Free software projects should welcome multiple implementations and interoperability, because these are the mother's milk of free software. It's frankly incoherent, given values of free software, that a reimplementation of, for example, Unix coreutils (GNU) would find fault with a reimplementation of itself (uutils).

Notwithstanding how philosophically incoherent it is, a desire, now that Linux and free software have some market power, to be a bully back, to grasp for monopoly power, to play AT&T, is really distasteful. What's exciting about free software is not the artifact, Linux or coreutils or sudo, but that anyone can create new and interesting alternatives.

Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by zorked on Tuesday November 07, 2023 @05:44AM (#38175341)
The fact that it is free software shouldn't make things different since it's a matter of copyright law. It's fine to copy the interface - the implementation not really. There would certainly be NO problem if a close reimplementation was under the GNU GPL (as a derivive work). But a close reimplementation can't have a different license.
Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by zorked on Tuesday November 07, 2023 @08:11AM (#38176335)
*derivative work
Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by slikrick on Wednesday November 08, 2023 @08:24AM (#38189976)
a reimplementation that copies the interface has no need to copy the license. GPL people just get scared because they know their license can't prevent people from rewriting their own software (of course, such an idea is ridiculous).

the GPL is not a perfect license, there is no such thing.

Re:The First Stable Release of a Rust-Rewrite Sudo Implement... by mustache_kimono on Tuesday November 07, 2023 @10:18AM (#38177746)
This was a discussion of the philosophical/meta/attitudinal issues, and why this is kinda a bizarre attitude for a free software project to hold.

You might take a look at another comment of mine about why I think there may be few legal/copyright issues with a reimplementation: https://news.ycombinator.com/item?id=38164958

Implicit in your comment are unstated assumptions about what is copied from the implementation. Suffice to say -- I disagree that a so-called "clean room" implementation is always required re: software published on the internet, or that the act of simply reading GPL code taints one forever, re: that code. The reason why is the reason why reading a book does not taint one forever and prevent one from writing one's own book. See, and pay close attention to the "Merger Doctrine": https://en.wikipedia.org/wiki/Idea–expression_distinction

I'd agree if there is something especially clever/creative about the implementation that the reimplementation copies, that might be an issue, but again it seems especially rich for a reimplementation to find fault with a reimplementation ever.