You probably misunderstood. C can represent any program's semantics, since it's Turing-complete (modulo finite memory). C can't encode the lifetimes Rust uses, but those get erased during compilation to MIR. This takes MIR from rustc (where borrow checking has been completed and lifetime annotations erased) and outputs C with the same semantics. LLVM doesn't use tokens not produceable by C, but rustc does.
I think it's a reference to certain optimizations possible due to aliasing rules in Rust that are not possible (or maybe only "not straight forward", I'm not sure) in C. So a transpiled program while keeping its semantics might not still compile to equally optimized assembly.
IIRC C can do the same things with correct usage of `restrict`, but that's extremely difficult by hand. So difficult that LLVM's `restrict` support was very buggy when Rust first started using the capabilities. Those bugs got fixed, but it's still impractical to use in handwritten C.
Their customers largely aren't their users. Their customers are the purchasing departments at Dell, Lenovo, and other OEMs. Their customers are the purchasing departments at large enterprises who want to buy Excel. Their customers are the advertisers. The products where the customers and the users are the same people (Excel, MS flight simulator, etc.) tend to be pretty nice. The products where the customers aren't the users inevitably turn to shit.
"Banner blindness" applies to the rules/sidebar. The user sees it, notices it's not what they're looking to interact with, and ignores it. The same thing happens for modal dialogues where the user will click whatever button makes the message go away without bothering to read the message, only the button text.
A company that designs fonts. In the past they cast said fonts in metal to create movable type, a foundry is a place where metal is melted and cast into various forms. A font foundry was thus a place that made the type for printing presses.
It's a ton of work to design a font. Any designer can do it, not any designer can do it well. It's a very small niche of overall design. That led to a few companies specializing in font design, and predictably private equity firms have been buying them out & raising prices. Customers will switch away, but this creates unexpected work to do so some might end up paying at least for a while.
Same. It's had far fewer issues for me than X, even on Nvidia with my current laptop. Multiple monitors with different resolutions & thus different fractional scaling ratios just works, from the Plasma settings GUI. No need to edit any configs manually. That never worked out-of-the-box for me with X.
X11 applications will still "work" on Plasma Wayland session by utilizing XWayland, a tool that (afaik) runs a compact X11 session for each application.
What is being removed is running an X11-native Plasma session, only Wayland Plasma sessions will be available starting with Plasma 6.8.
NixOS is mostly a rolling-release distro, like Arch, but it rolls a bit more slowly. You can opt into full rolling release with the "unstable" branch, which is very common. There's not a lot of benefit to "stable" IMO.
Er, no it isn't? Yes, unstable is rolling, but otherwise it has releases, like 25.11, which contain breaking changes. It cuts new releases quite quickly and drops old ones fast, but that doesn't make it a rolling distro.
reply