5 ms·
Agreed for sure that working with C and C++ is the only way forward for systems languages. Rust's expression of this is the zero-cost C FFI, using native platfo
by steveklabnik 5y ago
Agreed for sure that working with C and C++ is the only way forward for systems languages. Rust's expression of this is the zero-cost C FFI, using native platform tooling, and stuff like that. Rust was never about re-writing the world, after all, its reason for existing was to eventually improve Firefox. The very first presentation about Rust (http://venge.net/graydon/talks/intro-talk-2.pdf http://venge.net/graydon/talks/intro-talk-2.pdf) says "We are not “rewriting the browser”. That's impossible. Put down the gun."
Zig's cross compilation stuff and general compiler features, that this post talks about, is excellent, awesome, and makes me quite jealous frankly.
- underdeserver 5y agoI admire your use of special quotes to not break my mental parsing of your quote.
- steveklabnik 5y agoHilariously it was a copy/paste situation that I went "oh, that's kinda neat, I'll leave that" so I'm glad you noticed. (I am often guilty of nesting thoughts (inside of other thoughts) which is kind of amusing (even though I've never found lisps particularly easy to read)).
- wyldfire 5y agoI think typical writing style guides suggest the single-quote for nested quotes. "I think he said, 'No way?! Zig for the win!'"
- kristoff_it 5y agoNot sure if this transpired in the writing, but my interpretation of RIIR, partially informed by the chat with JT [0], is that this is a sentiment that I guess is there in some people, but that it was never something officially sanctioned. [0] https://www.youtube.com/watch?v=X7ny7Qrsbd8&t=5391s https://www.youtube.com/watch?v=X7ny7Qrsbd8&t=5391s
- steveklabnik 5y agoIt is a weird self-fulfilling thing. People talk about it like it's a thing, so it's a thing, even if there's very little actual evidence of anyone sincerely holding this belief. People repeat that there's this plague of folks requesting that projects be re-written, and while it is literally true that I have seen two or three instances of this (you link to one of them, and notably it is not anyone harassing maintainers about their choices), it's been two or three. I actually got annoyed with this enough that I started doing a quantitative analysis; if you look at the canonical repository tracking this, it's got 44 total issues, most of which are jokes https://github.com/ansuz/RIIR/issues https://github.com/ansuz/RIIR/issues If you search GitHub for issues with these words in it, you get some, but many are either obvious jokes, people making issues on their own projects to think about doing this, and things like that. I never followed through on collecting it into a blog post though. I didn't think your writing was inappropriate at all; memes are memes, and I'm convinced that this one is just never going to die, because it's taken a life of its own, regardless of the underlying truth or not. It is always worth pushing back on this sentiment, even if I don't think Rust specifically tends to actually embody that sentiment very much. (Also: I don't know why you're now being downvoted. Hacker News works in mysterious ways.)
- kristoff_it 5y agoLooking forward to when we get our own unfounded never-dying meme :^)
- crazy_horse 5y agoWhy does it matter?
- steveklabnik 5y agoI think it matters less and less, which is part of why I didn't follow through on publishing. As to why it used to matter, well, it is tremendously difficult to bring a new programming language into popular usage, and even more in the systems space. It requires tireless effort by a large number of people. It is a very fragile thing. The stories we tell ourselves and others matter, and they influence what happens. That's all I'm willing to say right now :)
- deleted 5y ago[deleted]
- fulafel 5y agoThe boat has already sailed, but it's GCd languages and not Rust that replaced most usage of C and C++ in systems programming. Rust is nibbling at the remaining niche islands of C/C++.
- moltonel3x 5y agoRust isn't only nibbling at the C/C++ niches: thanks to its correctness and productivity aspects it also attracts people coming for example from Go/Python/Javascript. In some way, you could say that Zig is pulling system programmers towards high-level programming, whereas Rust is pulling high-level programmers towards system programming. That's not a watertight comparison but I think it's an insightful one.
- flohofwoe 5y agoSince Rust is built on top of LLVM, what's preventing it from "just" adding the Clang C/C++/ObjC frontends into the Rust compiler, and create cargo packages with cross-platform C/C++/ObjC headers and runtimes? This would make cross-compilation and C/C++/ObjC integration just as easy as with Zig (and without requiring any external C toolchain, which is the most important point). I guess the other (simpler) alternative is to wrap Zig into a Cargo package, similar to this: https://pypi.org/project/ziglang/ https://pypi.org/project/ziglang/
- steveklabnik 5y agoTechnically? Nothing that I'm aware of. Practically? The desire to do it, and the engineering work required to make it happen. I have been talking about how much I would love this to happen, but I can't do the work myself. Frankly, I don't contribute to the compiler, so even getting up to speed would be a ton of work I just don't have the time for.
- AndyKelley 5y agoIf Rust compiler team members wanted to collaborate on this effort, I would be open to that. We could co-maintain a separate repository with: * The collection of headers for various targets, and the tools to upgrade/maintain them. * The source files for various libcs, patches, instructions/tools to upgrade/maintain them * A declarative set of instructions to create build artifacts (not Makefiles!!) * Instructions/patches needed to integrate Clang driver frontends into a different binary (making the "main" functions co-exist peacefully). Would be a fair amount of overhead to collaborate, but perhaps could ultimately save both parties labor.