dataking

The research is very likely under peer-review so it is very likely that the site will be revised once the paper is accepted and presented at a conference. Just everyone else, people in academic have more stuff to do than there are hours in a day. Be kind, please.

Immunant | Senior Software Engineer | REMOTE(US only) | Full-time | https://www.immunant.com

Do you want to get paid to use Rust? Do you know a thing or two about systems programming, compilers, and operating systems? Do you like to research new approaches with some of the smartest people in the field? Immunant is helping deploy Rust code at scale alongside or in place of C/C++. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you are self-motivated, have demonstrable experience with C/C++/Rust, and an eye for detail, we should talk.

We are located in Southern California but consider remote candidates anywhere in the United States.

More details: https://www.immunant.com/jobs, https://www.github.com/immunant

Send questions and applications to team@immunant.com – please mention HN in subject line. We look forward to your application!

I bet you'd also be real stuck on what possible value Apple could bring to building a phone. All the bits that made a feature phone valuable were also outside of Apple's competencies. Thing is, cars are becoming more like computers.

Immunant | Senior Software Engineer | REMOTE | Full-time | https://www.immunant.com Do you want to get paid to use Rust? Do you know a thing or two about systems programming, compilers, and operating systems? Do you like research-y work with some of the smartest people in their field?

Immunant is helping deploy Rust code at scale alongside or in place of C/C++. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you are self-motivated, have demonstrable experience with C/C++/Rust, and an eye for detail, we should talk.

We are located in Southern California but consider strong remote candidates anywhere in the United States.

More details: https://www.immunant.com/jobs Code: https://www.github.com/immunant

Send questions and applications to team@immunant.com – please mention HN in subject line. We look forward to your application!

CSmith [0] also made significant strides in that area.

[0] https://embed.cs.utah.edu/csmith/

Cool project. One of the best decisions we made for C2Rust was to use clang to parse C code (which is also the recommended approach by the author of Corrode). It looks like C2nim is rolling its own C parser for now; that's eventually going to become a limitation as the project expands to cover more of C.

> No field has more idiots than economics.

Alternative explanation: economics is hard & illusory superiority is a thing.

tl;dr: hackintoshes may stop working 'cause arm. nothing new behind the clickbaity title.

interesting idea that I'm loath to follow as I enjoy having my passwords auto-filled from my password manager - particularly on mobile.

That doesn't sound like good news for the hackintosh community.

> Once you get over the fact that the code makes your eyes bleed, it has a sort of beauty.

as a c2rust contributor, this made me smile :) thx friend!

I agree with the concerns over complexity. That said, I see nothing in the article that indicates that a firewall appliance is the correct countermeasure. Defense in depth is likely what you need (and may ultimately get) here.

Immunant | Senior Software Engineer | REMOTE | Full-time | https://www.immunant.com

Do you want to get paid to use Rust? Do you know a thing or two about systems programming, compilers, and operating systems? Do you like research-y work where the best solution is rarely the most obvious one?

Immunant is helping its customers deploy Rust code alongside or in place of C/C++. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you are self-motivated, have demonstrable experience with C/C++/Rust, and an eye for detail, we should talk.

We are located in Southern California but also consider strong remote candidates in the United States.

More details: https://www.immunant.com/jobs Code: https://www.github.com/immunant

Send questions and applications to team@immunant.com – please mention HN in subject line.

We look forward to hearing from you!

Immunant | Senior Software Engineer | REMOTE | Full-time | https://www.immunant.com Immunant's mission is to make it easier to deploy Rust code alongside or in place of C/C++ at all levels of the stack. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you have demonstrable experience with C/C++/Rust, an eye for detail, and plenty of self-motivation, we'd love to talk.

We are located in Southern California but also encourage strong candidates who wish to work remotely in the US to apply.

More details: https://www.immunant.com/jobs Code: https://www.github.com/immunant

Send questions and applications to team@immunant.com – please mention HN in subject line.

We look forward to hearing from you!

I wondered the same. I think they are. You can see how the pool is very cramped and follows the curvature of the submarine hull.

Rust's type system is complicated for a reason. It makes explicit the reasoning that is necessary to allocate and access memory correctly without reference counting or garbage collection. Sure it is easier to start writing C but I believe it is overall faster to write and debug a Rust program because C requires additional sanitization and fuzzing to catch errors.

To quote Grissom from CSI: I've learned that sometimes you can go faster by going slow ;-)

Compilers such as clang/LLVM and GCC do support a memory-safe mode (e.g. AddressSanitizer) which is not what you want because they add large overheads and thus are not intended for production use.

There's an ongoing effort to design extensions to C that allows efficient enforcement of memory safety, Checked C from Microsoft Research is an interesting and current effort in this direction.

For all the challenges of getting comfortable with Rust (which I 100% acknowledge), it does provide a very interesting tradeoff between performance, safety, and compatibility with C.

Immunant | Senior Staff Engineer | REMOTE | Full-time | https://www.immunant.com

Immunant's mission is to make it easier to deploy Rust code alongside or in place of C/C++ at all levels of the stack. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you have demonstrable experience with C/C++/Rust, an eye for detail, and plenty of self-motivation, we'd love to talk.

We are located in Southern California but also encourage strong candidates who wish to work remotely in the US to apply.

More details: https://www.immunant.com/jobs Code: https://www.github.com/immunant

Send questions and applications to team@immunant.com – please mention HN in subject line.

We look forward to hearing from you!

Interesting idea but likely in violation of the GitHub Actions ToS [0].

> Actions should not be used for:

[...]

> any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.

At the very least, I recommend you highlight the Actions ToS to your users lest they miss this restriction.

[0]: https://docs.github.com/en/github/site-policy/github-additio...

Immunant | Senior Staff Engineer | REMOTE | Full-time | https://www.immunant.com

The team at Immunant is working tirelessly to make the lower levels of the modern software stack more secure. We are looking for a fellow systems programming expert to help us harden components used by hundreds of millions of users each day. If you have experience with C/C++/Rust, an eye for detail, and a high degree of self-motivation, we'd love to talk.

We are located in Southern California but are also interested in strong candidates who wish to work remotely in the US. More details here: https://www.immunant.com/jobs

Send questions or your application to team@immunant.com; please mention HN in subject line.

We look forward to hearing from you!

I think this comment is spot on. I've used cellular services in both Germany and Denmark extensively and they are nothing alike. Germany has spotty coverage; in Denmark, you have coverage pretty much everywhere even in rural areas. This is not just geography, it is also deliberate government policy.

I was also surprised they picked "Programming Rust" over "The Rust Programming Language" book.

While some patterns that call for unsafe today might be eliminated in whole or part, code that violates the ownership and borrowing rules will have to remain unsafe. I think fuzzing is not guaranteed to reach all unsafe code paths, nor provide full test coverage. Ideally, you want a) some sort of formal proof that the unsafe code cannot violate memory safety, b) 100% branch coverage for unsafe code, or c) both (because profilers and proofs can be wrong too :)

edit: grammar.

Except that scientists working on DARPA programs have also produced some technologies that have proven phenomenally useful to civilians such as the internet, computer mice, GPS, Siri, etc.

Good question. I agree that this is a problem but I wonder whether it is mitigated somewhat by search engine customization. I think the set of people that are simultaneously interested in Sumerian (the product) and Sumerian (all things relating to Sumer, the people of Babylon, etc.) is relatively small I imagine?

C2Rust contributor here. You are right that the transpiler preserves all the weaknesses of C in its output. (Thanks for taking a look :)

C2Rust includes a refactoring tool that (in some, currently very limited circumstances) let us lift raw C pointers to Rust references (to slices) as a step towards using safe Rust constructs. This is obviously not something that can be 100% automated but our goal is to see how far we can reasonably go. Lots of work ahead but we 100% agree that some level of automation is highly desirable here.

C2Rust contributor here. Yes, the conversion to unsafe is indeed only intended as a stepping stone for a rewrite into idiomatic Rust. In fact, we're hard at work on a refactoring tool that will (hopefully, one day) take some of the tedium out of that process by doing things such as identifying raw pointers that can be upgraded to proper Rust references.

Scope guards seem like a really good idea. Has there been any effort to write a C to -betterC transpiler just like there has for Rust (e.g. C2Rust [0], Corrode [1])?

[0] https://www.github.com/immunant/c2rust

[1] https://www.github.com/jameysharp/corrode

I don't think that is necessarily true. Rust has only one compiler (and I think adding a second one would be a huge effort with no clear win) yet it is developed by a community that is very welcoming to newcomers. At least, that's been my experience.

> Finally, I have to say, I loved using Rust. It’s the least mental overhead I’ve had to maintain with a systems language, and it was a blast to use.

This mirrors my experience learning Rust while working on the C2Rust translator (HN discussion https://news.ycombinator.com/item?id=17381946). Great read!