3 ms·
> then points out that rustc can't compile itself on i386, which is relevant… how? Remember he is speaking as the leader of an operating system project. As in
by asveikau 9y ago
> then points out that rustc can't compile itself on i386, which is relevant… how?
Remember he is speaking as the leader of an operating system
project. As in, a basic part of the project functioning normally is compiling the whole thing from scratch. If something needs cross-compilation to even get started it won't end up in OpenBSD base.
I seem to recall when it supported more architectures they made a public show about how they weren't going to cross compile even for targeting wimpy/sluggish machines, because recompiling the OS was a good stress test for the kernel itself.
- sitkack 9y agoAnd thus they lock themselves into the lowest common denominator as they target smaller systems. This is ridiculous. OpenBSD looks like performance art, literal security theater.
- asveikau 9y agoDo you use it? I have had it on one machine or another since around 2000, and I have by and large been pretty happy with it. Not every personality type will like it, and sometimes they do make odd decisions, but it is pretty well put together. Another point about the *BSDs, something doesn't have to be in base for you to use it. The base system is supposed to be small and not have a lot of dependencies. You are free to use things in ports and packages or compile them yourself. So this is not the same as never being able to use rust.
- mitchty 9y ago> And thus they lock themselves into the lowest common denominator as they target smaller systems. This is ridiculous. OpenBSD looks like performance art, literal security theater. Those lowest common denominator systems tend to find bugs not present elsewhere. And stating that openbsd looks like performance art and security theater seems to indicate you haven't looked at what openbsd has done for security.
- sitkack 9y agoOpenBSD can be security theater and still do great things. But at some point sticking to an 90s Unix/C aesthetic looks deeply anachronistic. Yes, bugs are found at boundaries and interfaces, large or small. Something has to be different for the output to be different. If someone writes a bug proof TLS implementation while at the bottom of the pool wearing SCUBA gear, it is still security theater.