You can compile an older toolchain with mrustc (which is a C++ project), and then work your way up to the recent version.

"Unsafe" sections in Rust are typically small isolated code blocks, in contrary to legacy system programming languages like C and C++, where the entire application is unsafe.

No, you cannot corrupt memory outside of unsafe block. As far as I remember, there was one compiler bug where you could bypass the borrow checker with some very tricky code, however I don't think you can find this in production.

I am using Rust for over 10 years, since version 1.0, and it delivers, regardless of various social dramas around it. Besides, from my experience, the majority of "religious zealots" are actually the ones attacking the language and the community, which is, by the way, very friendly.

P.S. "Rewrite it in X" is as old as the programming itself, but there wasn't yet such a major step forward in the whole industry in the short term. Also Rust is a pleasant language to use, regardless of it's safety guarantees, so it's natural that people like it and do a rewrites. I don't see a problem with that.

On KDE Plasma desktop use "Super" (or "Win") key and right mouse button to resize the window no matter where mouse cursor is as long as it is inside the window. And window borders can be customized with thickness. And the resize handle can be toggled on or off. And the roundness of corners can be turned off. Don't thank me.

Whether is it a new shiny ultra-hyped CachyOS, or Manjaro, EndeavourOS, Omarchy, or a plain Arch, unless you want to spend most of your time configuring it, troubleshooting broken packages or unbootable OS, I (as a desktop Linux user since 2002) highly recommend to look elsewhere. My personal preference is openSUSE Tumbleweed with Plasma desktop for the following reasons:

• Rolling distro, always up to date
• Stable via their automated OpenQA testing system
• Built-in snapshots with easy rollback in case of update issues
• Plasma desktop is a first class citizen, latest version is highly polished and stable
• In general is rock solid, there is simply no need to use anything else

Portions of the Rust code can be marked as "unsafe". Within an unsafe block you can dereference a raw pointer and call an unsafe function (e.g. an external C function). Outside of the unsafe, the compiler guarantees memory safety and absence of data races, during compilation. Unsafe blocks are necessary to interact with the hardware, call external libraries written in other languages or write a highly optimized or specialized code.

While the entire application written in C (and C++) is inherently unsafe by design, with Rust you have isolated code blocks, which makes it much easier to review and find any potential bugs.

Official book reference

Recent KDE Plasma versions are stable, polished, fully customizable. Perfect? probably not, there are some occasional issues, but nothing truly irritating. I use openSUSE Tumbleweed (rolling distro) as a main OS on my laptop and desktop. While many distributions focus on GNOME environment, Tumbleweed has first-class support for Plasma. Wayland works great out of the box, also for most third-party apps. Built-in snapshot support makes sure the system stays stable all the time. As a software engineer, I think it's the best setup I can have today.

As it requires 32 GB of RAM.

Yes and not because "they are done", but also because few people are really interested in maintaining and expanding GNU code written 30 years ago in the language which isn't appropriate anymore to write anything beyond the very low-level OS kernels.

Or may be because C++ isn't fun to work with at all and it introduces no real advantages because it has the same fundamental issues as C.

C++ has no traits, no thread safety, no built-in utf-8 strings, no proper macros, no immutability by default, it is still inherently unsafe even without using the raw pointers.

Why not, it will be an interesting project and I can only welcome it. I don't understand your point in complaining that some people are busy doing something that you don't like.

Well I did, but funny enough, most people who complain about Rust language know absolutely nothing about it and just repeat the common FUD.

Not many, but there are some discovered: https://www.cve.org/CVERecord/... and who knows how many undiscovered. And it's not only about the existing code but also adding a new code.

Well, even without it's built-in compile-time safety, Rust is a modern language with a lot of features missing in C (just naming a few like traits, generics, utf-8 strings, FP-style constructs, immutability, standard library, thread safety, async, etc.), and it is much more attractive for the new developers.

It's not about memory leaks but memory safety and much better maintainability that legacy GNU C code. For logic errors there is a comprehensive test suite.

I have a hybrid Volvo V60 which is a fine car (fast, spacey, comfortable), but the infotainment system is a nightmare. Based on AAOS, it is riddled with bugs and is quite sluggish. New software releases do not happen often, and sometimes introduce more issues after update than fix them. Yes, you have access to Google Maps and Play Store, but the app selection is very limited and what's the point anyway if most can be only used while parked.

Comes with a must have accessory for every Apple touchscreen user: a rag for only $99.99.

One area where it shines is localization. "Hey bot, find all English strings in the code enclosed in double quotes, for each string create a key in the form 'category-description', for example error-not-found, create a translation file in Fluent format in the form of "key = value" for all those keys and their values. Do that for the following locales: ..."

With some prompt refinements, corrections, etc, done in 2 hours. Saved me 2 weeks of manual work.

Apple customers will pay anyway even if they double or triple the price.