Counterpoint, I believe the Swift syntax strikes a much better balance than Rust in terms of ergonomics and argument labels are awesome for designing fluent APIs. There are things that Rust does better, aside from having a bigger ecosystem, namely the whole borrowing/ownership system, though they're catching up (noncopyable types and references are coming soon).
The concerns about ARC are generally a bit overstated, ARC only comes into play with classes, which modern Swift greatly deemphasizes in favor of structs, enums and protocols. Sure, sometimes you need them, especially when interoperating with Objective-C, but Rust has its escape hatches for reference counting too (Rc/RefCell, Arc/Mutex), those are just (intentionally) a bit more verbose.
In short, Swift encourages a very similar, value-oriented programming style as Rust with a modern type system (generics, associated types etc.), while offering lots of nice syntactic sugar (property wrappers, result builders 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.
To be fair, the gaming chair also holds you against lateral GeForce
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.
Why not just add a timestamp that rotates every, say 5 seconds, to the hashed data?
That would make it infeasible to precompute the table permanently (it would have to be precomputed for a very narrow attack window, which is still better than nothing)
A nice example of this is Ardour: A DAW that's free in the sense that the source code is GPL, but the prebuilt official binaries have to be paid for.
How so? It's a polished Unix desktop that runs most open-source and a bunch of proprietary apps, including Final Cut and Logic. It's natively POSIX and has a proper shell.
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
In principle you can, the Mach-O format is openly documented and implemented in the major compilers. The issue is that you need a sysroot (aka SDK) of the frameworks and headers for your target OS, which in Apple's case are proprietary and cannot be redistributed legally (you could probably rip them out of a macOS installation yourself though). For iOS apps you'd also need to sign the binaries and install the app to the device which is non-trivial to impossible to do on other platforms.
Did you focus the popup containing the Touch ID symbol? Often times it opens defocused and you have to click it to actually use Touch ID.