Yeah, C libraries can be used in basically any mature language. It’s just too useful not to have.
And Rust, since it doesn’t need a runtime, can emulate the format of C libraries.
Rust libraries can also specifically target Python via pyo3.rs, but as I understand, this just does the C library format, plus a basic Python wrapper to make it nicer to use.
Sorry, I meant in the context of OPs question (so i guess up to them to set the rules). As in, you pick Python for the rest of your life, does that lock you out of C libraries? Its a bit of a rabbithole though, as many language runtimes would get excluded as well. There arent many languages that actually stand alone.
Ah, right, my interpretation is that as long as you don’t need to touch the source code, you’re good.
But yeah, it’s certainly not as clear cut. My pick would actually be Rust, because you can use it for pretty much everything, including web frontends via WebAssembly.
However, in that case, you still write HTML+CSS, which technically may or may not be programming languages, and the DOM API is actually only documented in JavaScript. So, I wouldn’t need to write JS, but would still want to read it…
Knusper@feddit.de 1 year ago
Yeah, C libraries can be used in basically any mature language. It’s just too useful not to have.
And Rust, since it doesn’t need a runtime, can emulate the format of C libraries.
Rust libraries can also specifically target Python via pyo3.rs, but as I understand, this just does the C library format, plus a basic Python wrapper to make it nicer to use.
CameronDev@programming.dev 1 year ago
Sorry, I meant in the context of OPs question (so i guess up to them to set the rules). As in, you pick Python for the rest of your life, does that lock you out of C libraries? Its a bit of a rabbithole though, as many language runtimes would get excluded as well. There arent many languages that actually stand alone.
Knusper@feddit.de 1 year ago
Ah, right, my interpretation is that as long as you don’t need to touch the source code, you’re good.
But yeah, it’s certainly not as clear cut. My pick would actually be Rust, because you can use it for pretty much everything, including web frontends via WebAssembly.
However, in that case, you still write HTML+CSS, which technically may or may not be programming languages, and the DOM API is actually only documented in JavaScript. So, I wouldn’t need to write JS, but would still want to read it…
CameronDev@programming.dev 1 year ago
Thats probably the best way to look at it, otherwise it gets very difficult very fast.
If markup languages are locked out, then rust has other problems, because you then can’t change your cargo.toml file anymore.
And then there is the build script problem :/
As a thought excercise this has been interesting, there certainly are a lot of inter-dependencies between languages the deeper you look.