Viewing profile — UtherII

That's exactly the point. The patch in question is not to be used in any part of the kernel. It is a wrapper around the C API. It has no impact on current code and it will only be …

The concept of safety is pretty different in a kernel and in a programming language. The kernel can be attacked directly with malicious calls, while it's the program created by the…

Have you really used Rust on big codebases? One of the big advantage of Rust is especially that it fails far earlier than C++. Borrow checker error are local error that prevent bad…

The java slow build time is usually a dependency problem too. On similar complexity, Java is usually as fast or even faster than Rust.

It can used as an intermediate language, and since it was the only way to run code on the browser without plugins before WASM, it happened a lot. But nowadays WASM is much more sui…

You can even go back earlier : MessageFormat is available in Java since 1997.

I not sure he mean never panic at runtime. I think there are good reason to panic at runtime if you care about safety a buffer overflow is a good reason for instance. But a memory …

You have to blame both the carpenter and the tools. Since there is no such a thing as a perfect carpenter, mistake will happen, that why a tool that can prevent a whole category of…

The IDE support use to be very poor but nowadays there are two really nice contenders : - Jetbrains IDE with the Rust plugin (maintained by Jetbrains itself). The free IntelliJ IDE…

The problem would be to get a definition of idiomatic code. Would it be fair to accept an optimization on a language and refuse it on another because it is not idiomatic ?

I'm not so sure. I remember a presentation of Webrender with nice demos : https://www.youtube.com/watch?v=erfnCaeLxSI&spfreload=10 Everything was perfecty smooth, but according to …

A new programming language is not required, it's just a bonus to help developers handling safety and concurrency.

The most obvious case is bound checking. If you have a code with direct array indexing you have to use unsafe code or loose a little bit of performance.

That's why on Linux, by default, Rust link everything statically except the libc. But you sill can make a fully static executable by using the "musl" target.

Yes, the crash can come from every line of code, but the origin of the bug is in the unsafe code. That's why unsafe code has to be cleanly inspected to be sure it has a safe interf…

C++ has no advantage over Rust in this regard : C++ and Rust does not have stable ABI. But both can use the C ABI when a stable ABI is needed.