It is a big deal even after you know how it works.

The thing is, the languages like Rust only make this easier within their controlled "garden". But for C and C++, you build in the "world outside the garden" to begin with, where you are not guaranteed of everyone having prepared everything for you. So, it's harder, and you may need third-party tools or putting in some elbow grease, or both. The upside is that when rustaceans or go-phers and such wander outside their respective gardens, most of them are completely lost and have no idea what to do; but C and C++ people are kinda-sorta at home there, already.

▲

steveklabnik 4 days ago | parent [-]

What is "outside the garden" for Rust?

▲

einpoklum 4 days ago | parent [-]

Oh, say, use some binary C library with some header, that you found on some system.

▲

hiimkeks 4 days ago | parent [-]

That shouldn't be too tricky, assuming the binary is built for the sort of device you want to run on. At least not much more complicated than calling any other C code, using bindgen.

	▲	steveklabnik 3 days ago \| parent [-]
		Yep, Rust made design decisions to make this case as zero overhead as it can be.