8 ms·
> I wasn't implying. I was stating a fact. There has been no attempt to move the smallest parts of the ecosystem, to provide replacements for base POSIX utili
by jcranmer 7y ago
> I wasn't implying. I was stating a fact. There has been no attempt to move the smallest parts of the ecosystem, to provide replacements for base POSIX utilities.
This is in fact incorrect--there is a project aiming to build all of the coreutils in Rust (https://github.com/uutils/coreutils https://github.com/uutils/coreutils).
More to the point: while I do concur in the conclusion that Rust shouldn't be a part of the OpenBSD base system, the gatekeeping implied here (it's not a serious language because it's not used to build an operating system) is really toxic. Especially considering that the gate in question has already been thoroughly breached by the language in question (some universities have switched to using Rust in their OS courses, for example).
- deleted 7y ago[deleted]
- zdw 7y agoLinked mailing list message is from 2017, which is may be after when the linked project was started/viable.
- tpush 7y agoNo need to speculate, if you follow the GitHub link you'll see that the project is older than 2017.
- protomyth 7y agoHow many utilities were rewritten and shipped at the time of the post?
- ChristianBundy 7y ago79 by my count, but I'd be happy to have someone correct me. https://github.com/uutils/coreutils/tree/ef4d09ee3c067c280bacb106524b5b43a557c4d9#utilities https://github.com/uutils/coreutils/tree/ef4d09ee3c067c280ba... It looks to me like the only changes in that table since November 2017 are that `join` and `df` were moved from 'todo' to 'semi-done'.
- protomyth 7y agoAre they done, or did they move onto to something else?
- ChristianBundy 7y agoI don't know.
- wang_li 7y agoYou’ll also see that cp, ls, expr, test, and others are still only considered semi-done.
- jcranmer 7y agouutils was started in 2013, and was decently complete well before 2017.
- jerf 7y agoYour definition of "decently complete" and Theo's are likely to be waaaaay different... and within your respective contexts, you are both correct.
- skrebbel 7y agoYou make valid point, but you can't fault Theo for predicting a different future in 2017.
- loup-vaillant 7y agohttps://github.com/uutils/coreutils/commit/d4e96b33e343733992fad55ac840c9649cd72ede https://github.com/uutils/coreutils/commit/d4e96b33e34373399... I read 2013, Theo de Raadt's email is from 2017, over 4 years later. I think we can fault him for being overconfident and not checking his facts.
- geocar 7y agoThat commit doesn't have any files in it. The first release of "uutils coreutils" appears to be this: https://github.com/uutils/coreutils/commit/511f138e3856e2d690ba08c5893c8ee1abd0e37a https://github.com/uutils/coreutils/commit/511f138e3856e2d69... which is only twenty days young, and a 0.0.1 release to boot (whatever that means).
- gmanley 7y agoThe first four utils were added 7+ years ago: https://github.com/uutils/coreutils/commit/9653ed81a2fbf393f420d9a8007c574d922018d1 https://github.com/uutils/coreutils/commit/9653ed81a2fbf393f... This has been developed for a while. You're looking at the official GitHub releases which doesn't mean much. It just means they just started providing official compiled releases. Not all projects even do that at all. I know a lot of people getting into Rust, including myself, started reading through this repo. This was one of the first good real-world examples of Rust, that I found.
- geocar 7y ago> You're looking at the official GitHub releases which doesn't mean much. Fermat would like rust then.
- loup-vaillant 7y ago
- protomyth 7y agoThe post was written in 2017. How far along was the project in 2017. Also, I am a bit confused about the gatekeeping implied here (it's not a serious language because it's not used to build an operating system) is really toxic.? Which line in the e-mail stated that?
- jcranmer 7y agoThe gatekeeping is strongly implied by this statement: > As a general trend the only things being written in these new languages are new web-facing applications, quite often proprietory or customized to narrow roles. Not Unix parts. Which I read in the tone of "go play with your toy language somewhere else, and let the real programmers program with real languages. Additionally, there's the allusions to the fact that the ls/grep-replacements in Haskell aren't POSIX-compliant, which I again read in the tone of "they can't be taken as serious replacement efforts."
- protomyth 7y agoThat tone seems more you than Theo. OpenBSD isn't known as a first mover operating system for new technologies. If the utilities are rewritten and not compatible then it really isn't a rewrite, its a new program with the same name as a previous program. Frankly, if they don't implement that standard, they aren't serious replacement efforts. They could be useful and maybe the options omitted aren't important to the person implementing it, but they are not suitable to replace the current utilities.
- rootlocus 7y ago> As a general trend the only things being written in these new languages are new web-facing applications, quite often proprietory or customized to narrow roles. Not Unix parts. That doesn't imply "real programmers program with real languages". It implies they're not used to enrich the UNIX / open source ecosystem, which might imply there's not a real need for them in the official repositories, since they're not used to build anything else in the repository. > Additionally, there's the allusions to the fact that the ls/grep-replacements in Haskell aren't POSIX-compliant, which I again read in the tone of "they can't be taken as serious replacement efforts." There is real value in being "POSIX-compliant". It means programs respect an interface. If I write a script that uses "grep" or "find", I have strict requirements from them. I expect them to take certain arguments and interpret them in a certain way. If I can't simply replace "grep" with "haskell-grep" and get the same results (with stronger safety guarantees or performance), I may not have a use for them in certain scenarios. The critique that "They are completely different programs that have borrowed the names." doesn't imply "they can't be taken serious", it implies they can't be used to replace the existing ones.
- dirtydroog 7y agoIs it 'really toxic', or just uninformed? Note that the email conversation was from a few years ago.
- loup-vaillant 7y agoI'd say toxic. When you point out that "nobody has done this" in this way, there is a strong implication that it's not possible, not reasonable, or not wort the effort. Rust explicitly aims to be a systems language. It explicitly challenges C and C++ on their own turf. Implying that it's not suitable for serious systems work is insulting. > Note that the email conversation was from a few years ago. Remember that the project he said didn't exist was 4 years older than his email. And if I understand other comments correctly, that project was well known among Rust practitioners. He made strong claims outside his area of expertise. An easy mistake to make, but one that has consequences when you're this famous. Such mistakes are totally fine in private, but in public… they're a little toxic.
- allp10 7y agoRust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad. Rust good, C bad.
- loup-vaillant 7y agoMeta: if someone could explain to me where the 5 downvotes come from, I'd be curious to know which part of my comment triggered them. Is Theo de Raadt above criticism? Is Rust actually failing at its primary goal? Are words like "toxic" and "insulting" under a soft ban? Right now all I have to go by is a dead flagged strawman from a throwaway account.
- dirtydroog 7y agoDon't worry about it. My comment seems to be up and down like a yoyo.
- dathinab 7y agoNot only does coreutils exist there is also another think which shouldn't be forgotten. When you re-write a tool, _why not improve it_? (Especially if the chance that the 100% backwards compatible rewrite will not be accepted anyway). For a bunch of tools exactly this happens, a new tool which provides the (roughly) functionality but a new (IMHO often better) interface, slightly different options or syntax (for got reasons). Etc. An example for this is ripgrep (rg), which already became a widely used replacement for grep. It's just not a drop in replacement. (It couldn't do what it does if it would be).
- notaplumber 7y agoBSD does not use GNU coreutils. Is it really unexpected that the developer of a BSD project might have been unaware at the time of a project attempting to replace it, or simply found it incompatible with the stated requirements-- POSIX compliant base utilities. OpenBSD does not care about compatibility with GNU, for example longopts do not work for many utilities, with exceptions to permissive replacements to historically used GNU utilities (grep example). It also does not address the concerns of higher build times compared the contemporary C counterparts, which also support far more platforms than Rust. The use of cargo for example suggests that at least a few uu utilities makes network connections at build time to fetch dependencies! For example something as simple as chown: https://github.com/uutils/coreutils/blob/master/src/uu/chown/Cargo.toml https://github.com/uutils/coreutils/blob/master/src/uu/chown...
- jen20 7y agoThe use of cargo implies this no more than the use of make. One can fetch all dependencies and then build in a completely offline manner.
- jcims 7y agoI think it's OK for platforms to have principles and if those principles are going to yield anything of value you have to be fairly consistent and ruthless about them. There was a little bit of editorializing there but if 'base builds base' is table stakes then start working on that coreutils project first.
- creddit 7y ago> the gatekeeping implied here (it's not a serious language because it's not used to build an operating system) is really toxic. He's not gatekeeping in that way by saying that Rust isn't used to create OS utilities (which as an aside is what he actually says. He doesn't say anything about building an OS) and therefore isn't a serious language and therefore shouldn't be included in OpenBSD*. He's saying it's not used for making OS utilities and therefore has no specific use in OpenBSD that requires it to be in the toolchain. Very different points with the latter being pretty reasonable, imo.
- asveikau 7y agoSome substantive comments I read from the mail: * It takes a long time for a rewrite to be fully compatible and a good implementation. This project says it uses the busybox tests and that seems like a good start. Is it good enough though? Busybox itself is quite good for certain embedded niches but it would be absurd to replace a good chunk of OpenBSD userland with that, the usability would suffer a lot. * OpenBSD needs to compile itself, in reasonable time, and at the time of the writing rust was slower than C at this and could not self host on 32bit x86 due to address space limitations. Has it been fixed?
- yellowapple 7y ago> Busybox itself is quite good for certain embedded niches but it would be absurd to replace a good chunk of OpenBSD userland with that, the usability would suffer a lot. Not to mention that Busybox (last I checked) uses a license unsuitable for inclusion in OpenBSD (which is trying to reduce the amount of GPL-licensed software in the base install).
- pjmlp 7y agoNot only that, there are several POSIX implementations in Ada. They just don't get exposure in FOSS land.
- justin66 7y agoDo any major Linux distros think uutils is good enough to ship as the default? Are they at all involved? They'd be infinitely easier to persuade to try something like this than a BSD. For OpenBSD it's probably always going to be a non-starter because of all the hardware they'd have to leave behind.
- cycloptic 7y agoThere is no gatekeeping. To actually achieve POSIX-compliance is not an easy task and requires lots of testing. If you don't do it then your replacement will break everyone's scripts. A distro maintainer will also want to retain compatibility with their supported GNU/BSD extensions so that's more work to add on. I would still agree with his statement at least as far as BSD is concerned. Outside of Redox I haven't seen any serious projects to implement POSIX compatibility. The Rust coreutils project is a good start but from their readme it looks like they are more aiming to achieve GNU compatibility on Microsoft Windows while being MIT licensed — I don't think anyone is seriously using it to build a BSD (or even a GNU) distro. If I'm wrong about that I'd love to hear it though. Rust is a good choice to write these things in but let's be realistic about the time frame required to rewrite everything. Plus I just downloaded those Rust coreutils and tried to build it and now I'm waiting for 400 (!!!) Rust dependencies to download and compile. Is this really appropriate for a core system component to have this many dependencies? Or is there something I'm missing here? I admit I am not familiar with best practices in Rust. As the project stabilizes I assume they will want to start eliminating the dependencies or vendoring them upstream? At what point do we decide to put these into a separate library like libbsd or gnulib?
- notaplumber 7y ago> Is this really appropriate for a core system component to have this many dependencies? Absolutely not. The entire OpenBSD base system can be built without an internet connection.
- gjvc 7y agoThere is nothing sinister being implied by wishing to maintain the course that the OpenBSD project has taken. This leadership may not please all of the people all of the time (least of all non-dependent external projects), and it has no obligation to do so.
- ajross 7y ago> the gatekeeping implied here [...] is really toxic It's Theo de Raadt, toxic rhetoric is sort of his brand. But... he has a real point here. It's not about grep or cat or whatever really, those are just the use cases for which OpenBSD would care. It's that as Rust is reaching the second decade of its history, and despite some outrageous wins in press, evangelism, and general developer mindshare... Rust just hasn't made much progress in replacing exactly the software that it claims to be intended to replace! Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. After ten years of Rust success! It's not like no one is using Rust. It's not like it doesn't have success stories (even in the categories above). But they're comparatively rare, still. There's nothing in Rust that rises to the category of "stuff everyone just uses because it's what everyone uses" (c.f. zlib, libjpeg, readline...) yet. And if there isn't after the first decade, what needs to change to make it happen in the second. I mean, is it maybe fair to say that the window is closing for rust to take over a significant fraction the systems programming world?
- steveklabnik 7y ago> It's that as Rust is reaching the second decade of its history Sort of. It's only been five years since it was actually stable enough for production use. (with a few exceptions of folks who were really invested)
- comex 7y agoAnd: > Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. How many of those projects in any language are less than five years old? The ubiquitously used stuff is mostly much older. But among the projects which are that young, Rust has substantial representation.
- jerf 7y ago" There's nothing in Rust that rises to the category of "stuff everyone just uses because it's what everyone uses" (c.f. zlib, libjpeg, readline...) yet." IMHO, that's basically not possible, so it isn't a fair ask. If the Rust community produced a drop-in replacement that is every bit as good as readline in literally every way... still nobody would switch, because why would they? What's the benefit? You spend all this effort just to trade evenly across. If the Rust community produces something better, nobody's going to use whatever those extra features are outside of Rust itself. This is the category of software that will be last. The question for Rust, and equally, every other ambitious language, isn't really "What percentage of existing code will be rewritten in this new language?" (And by "rewritten", I don't just mean "reimplemented but only your community uses it, but in the sense you mean... it actually replaces the original.) If your answer is any number significantly over zero, that itself represents entrance into the absolute top tier of languages... this is very rare. The question for Rust et al is "What percentage of future code will be written in your language?" On that front, Rust is still on a pretty decent trajectory.
- simias 7y agoHe's a maintainer, gatekeeping is literally his job. He's the one who decides what makes it in or not. His reply is not great, but IMO posting to some venerable old project's ML saying, in the abstract and without actually having made any effort to analyze the issue in depth "Under what conditions would you consider replacing one of the current C implementations with an implementation written in another, "safer" language?" comes off as rather rude and not very productive IMO. I can understand him shutting it down immediately instead of wasting his time arguing with programming 101 students who cargo cult Rust without understanding the reality of maintaining something as complex as OpenBSD.
- gdy 7y ago>the gatekeeping implied here is really toxic The words 'gatekeeping' and 'toxic' are toxic.
- Ensorceled 7y agoAgreed, and it's even more toxic to use "gatekeeping" in this fashion for somebody who is LITERALLY a gatekeeper for the project under discussion.