Earlier quoted context omitted.
`unsafe` is already very prevalent in the ecosystem and this is a big point of contention. https://github.com/actix/actix-web/issues/289
This would be anecdotal, and caused massive stir in the community when it was realized.
Show HN: RustyBox – a Busybox fork written in Rust
31–40 of 56 posts
Re: Show HN: RustyBox – a Busybox fork written in Rust
#32Re: Show HN: RustyBox – a Busybox fork written in Rust
#33If this started with BusyBox translated from C to Rust, is this code also under the GPL, as is BusyBox? I don't see any LICENSE or COPYING files in the repo.
Re: Show HN: RustyBox – a Busybox fork written in Rust
#34Missing license.
Re: Show HN: RustyBox – a Busybox fork written in Rust
#35Re: Show HN: RustyBox – a Busybox fork written in Rust
#36Unless Rust suffers some catastrophic leadership or design choices, I'm convinced it will be the next language to "eat the world."
Re: Show HN: RustyBox – a Busybox fork written in Rust
#37If a GPL code is auto-translated to another language, shouldn't the fork have the same GPL license? Or does the new author get to put a new license?
Re: Show HN: RustyBox – a Busybox fork written in Rust
#38Re: Show HN: RustyBox – a Busybox fork written in Rust
#39Re: Show HN: RustyBox – a Busybox fork written in Rust
#40What is this used for? I am interested in contributing
busybox provides coreutils, with a focus on being as stripped-down as possible. in other words, busybox provides binaries like cat, ls, nano, sudo, etc. (basically enough to be able to do shell scripting) for use in memory-constrained embedded linux systems like internet routers or in-vehicle infotainment systems.