mhoyeNaescent suspicion: if a utility tells me the language it was written in before it tells me what it does or why it was created, I should start looking for alternatives immediately.
Benjamin Fry@mhoye I don’t think I can agree. The language picked tells me a few things about it, is it easy to build and install from source if you have to, does it have decent dependency management such that I can verify there are no security vulnerabilities in the chain, is it a language I know so that I might contribute to it, are tests easy to run, will it be fast and cheap to run?
PixelJones@bluejekyll @mhoye
Of course, you're right that the language, toolchain, & dependencies are important _features_ of a system (especially if it is a component that needs to fit into an existing ecosystem) but ... when _how_ something is built is touted above _what_ value it brings, you might as well be saying "Look, it is Hello World but in Prolang! Aren't I a genius."
Of course, you're right that the language, toolchain, & dependencies are important _features_ of a system (especially if it is a component that needs to fit into an existing ecosystem) but ... when _how_ something is built is touted above _what_ value it brings, you might as well be saying "Look, it is Hello World but in Prolang! Aren't I a genius."
@PixelJones @mhoye it depends. If something that is intended to be exposed to the internet, for example, and is built in Rust, I’m going to be inclined to believe it will provide more stability and security than say something built in C (or many other language choices).
The language choice based on intended uses is absolutely important as it can raise confidence in that applications ability to meat the goals you have.