It's difficult to find someone actively hiring for Rust jobs these days. I'd love to use it day-to-day but it's still pretty limited in industry.
But there are a few dedicated Rust job boards:
"rust jobs" vs "rust jobs I personally want to do" doesn't really back up the statement that there are no rust jobs available.
The compensation isn't there to match it. Neither is it like a COBOL type of situation where someone's mainframe is running on super niche language.
You are better off learning C++ or Assembly
Clojure developers have a different distribution of unobserved skills and motivations than JavaScript developers or Go developers. So the difference in average salaries could be due to the robustness of the language, due to the pockets of the industry that use them, due to unobserved skills and related reasons, or even due to differences in how much Clojure vs. other developers value amenities like the novelty of the task that they are working on.
It would be interesting to see more than just a comparison of averages. But collecting good data to capture the finer details is hard.
For example, you can have a population of 10,000 jobs, 9,000 of which is hiring for Clojure and 1,000 of which is hiring for Forth. If you sample the 9,000 Clojure jobs, then you might conclude that 100% of all 10,000 jobs are for Clojure. But in reality, only 90% are.
Instead, you can sample 100 of the 10,000 jobs at random. The expected value of the average of whether a sampled job is a Clojure job will be 90%. There will be noise but that can be statistically accounted for.
If the population that you want to draw conclusions about is, say, the complete universe of jobs ever offered in the US in 2021, it will be difficult to find either a data set that contains this universe or a data set that is arguably a random subset of the universe. So representativeness is hard.
You could adjust your population definition to achieve plausible representativeness. For example, take the population of all developer jobs at companies that had an IPO between 2018 and 2021. Maybe you have a way to compile this data set from some source. Then you limit the scope of your claims but you will be more credible.
Another thing that you can do is take an existing data set that you know to be representative and compare the distribution of job characteristics in your sample to that. For example, you might find that your sample is more likely to include web development jobs than your reference data set. Then you know that your sample is not representative, and you know in what way it isn't. Or you might find that your sample is comparable to your reference data set. This can give you some confidence that your findings generalize.
I don't know many Clojure devs who found their job looking for a Clojure dev job ad. Even the yearly state of Clojure survey has ~2400 responses.
The number of responses to the Clojure survey is barely representative for the size of the job market; otherwise you would have to expect millions of respondents for e.g. the JavaScript survey; people responding to such surveys are likely fans of the technology, not necessarily professionals who were hired to use the technology; of course there are also professionals among the respondents, but we don't know the exact proportion.
Really? Speaking from the Elixir perspective, I get recruiters messaging me with surprising frequency about senior Elixir SWE roles with base salary up to USD $200k; it doesn't seem like compensation is the issue, at least from my experience.