Not that specific tbh, most newer native languages these days are compiled and memory safe (Rust, Swift, Go, Kotlin Native, etc)

CMake can also emit its own errors during the configure step though, particularly if you have complicated build logic and/or lots of external packages.

That’s mostly still true, with the small caveat that the default prefix on arm64 macOS is /opt/homebrew rather than /usr/local, so you might have to add it explicitly to your PATH

Projects for Apple platforms usually also use .h, where it could mean anything from C/C++ to Objective-C/C++.

In practice, Clang handles mixed C/C++/Obj-C codebases pretty well and determining the language for a header never really felt like an issue since the API would usually already imply it (declaring a C++ class and/or Obj-C class would require the corresponding language to consume it).

If a C++ header is intended to be consumed from C, adding the usual #ifdef __cplusplus extern "C" {... should alleviate the name mangling issues.

or Swift, Rust has semicolons while Swift doesn’t

It’s open source though and they plan on adding Linux/Windows support in the future

Side note: Rust is the only of the three to have an ML-style type system, which is generally agreed upon as one of the most theoretically sound foundations. Also the point is that Rust does it precisely without requiring dynamic allocation, as opposed to Go, for example.

Not OP, but a pretty common reason is having a super-modular and hackable IDE that can be used to develop pretty much anything. Everything is JSON-configurable, all editors are webviews, so adding stuff like HTML rendering in Jupyter notebooks is almost trivial from a technical perspective. Fleet might be a step in the right direction, but still feels like a layer on top of IntelliJ, which is a beast in of itself, plus it is closed-source.

Also the approach of decoupling editors from the language support via LSP might be one of the biggest innovations in this space in recent years, IMO. Having a widely adopted and open protocol for language support effectively made Neovim, Emacs etc. a viable choice. It has spawned several high-quality LSP implementations, often directly supported by the compiler vendors, e.g. clangd or rust-analyzer.

Arguably Microsoft has been monetizing a bunch of services on top of VSCode too and they haven’t always stuck to their own principles (see Pylance, a closed-source language server that only runs in official VSC builds), but the LSP itself was still a pretty big net positive.

Swift does, though using the dollar sign rather than underscores

That article tells you how to set up syntax highlighting and run the command-line compiler by hand, not really comparable to IntelliJ… The article feels like a generic SEO post

Just wanted to point that rust-analyzer is the fantastic language server that powers the language support, and it runs in a lot of editors (VS Code, Emacs, Neovim, …)

This is all fun and games until you try moving a backup to a file system that’s case-insensitive