News for hackers. Stuff that matters.

A comment on The long goodbye to C. Parent comment

Re:The long goodbye to C by Rusky on Friday November 10, 2017 @04:59PM (#15673410)
In some ways, Rust fits that sort of ultra-tiny niche even better than C++. It doesn't have the POD/non-POD split that C++ has, it has a lot of built-in data layout optimizations, idiomatic code does far less copying, you can package up platform hardware definitions in crates, etc.

Of course C++ can just revert to being mostly C in these cases, and C is lightyears ahead in tooling and documentation here, but as a language I think Rust has a decent shot at that space.

[ Parent | on HN ]
Re:The long goodbye to C by AstralStorm on Saturday November 11, 2017 @02:43AM (#15675389)
I don't think so, just because modern C++ can coopt almost all Rust features with trivial style and tooling changes.

One of the benefits of being a truly actively developed language, as opposed to fossilized Java.

[ Parent | on HN ]
Re:The long goodbye to C by steveklabnik on Saturday November 11, 2017 @08:32AM (#15676291)
C++'s Core Guidelines have been worked on for the last two years, and weren't even trying to get full compatibility with Rust's guarantees, and still aren't really done yet. It's great work, but it's far from "trivial". If it were trivial to turn C++ into Rust, we wouldn't have bothered making Rust.
[ Parent | on HN ]
Re:The long goodbye to C by Rusky on Saturday November 11, 2017 @12:14PM (#15677112)
That's... not true at all. Even aside from the memory safety stuff steveklabnik mentioned in a sibling comment, C++ is struggling to get things like concepts, pattern matching, or modules, and had to do a lot of non-trivial work in the past to get things like move semantics.

And even then none of that solves the problems I mentioned in the comment you replied to.

[ Parent | on HN ]
Re:The long goodbye to C by pjmlp on Saturday November 11, 2017 @05:44AM (#15675797)
Java is only fossilized on Google's Android fork.

Who knows, maybe it even gets value types before the C++ community can agree what modules are supposed to be.

[ Parent | on HN ]