In professional settings the right people are usually the hardest to come by, and the most expensive part of the business. Recruiting is very resource intensive, some of your most expensive employees spend a lot of time figuring out ways to lure candidates in, discarding applications, running interviews and so on.
In software development it can take up to a year until someone has turned out to not be a good fit, because the systems are quite large and the first few months will in most cases be spent introducing the basics of them. That's a rather hefty investment for most companies, except the very large ones.
So as a manager, why would you bet on Racket? Unless you understand the peculiarities and power in macros (and eager to teach it over and over again) you won't, because the board will roast you over bringing in the risk that you can't find replacements when core developers inevitably move on.
If there was something unique you could only use if you had Racket developers it would pull in broader industry usage, but as far as I know no such thing exists.
As a single or few developer consulting business/dev boutique things change, you'd only have to convince customers and they like shiny things that solve their problems or make money, and if you and your comrades know Racket well you could very well create such shiny problem-solvers relatively fast. Then you'd only have to resist the attraction of better pay and someone else closing the sales once the business is up and running.
In software development it can take up to a year until someone has turned out to not be a good fit, because the systems are quite large and the first few months will in most cases be spent introducing the basics of them. That's a rather hefty investment for most companies, except the very large ones.
So as a manager, why would you bet on Racket? Unless you understand the peculiarities and power in macros (and eager to teach it over and over again) you won't, because the board will roast you over bringing in the risk that you can't find replacements when core developers inevitably move on.
If there was something unique you could only use if you had Racket developers it would pull in broader industry usage, but as far as I know no such thing exists.
As a single or few developer consulting business/dev boutique things change, you'd only have to convince customers and they like shiny things that solve their problems or make money, and if you and your comrades know Racket well you could very well create such shiny problem-solvers relatively fast. Then you'd only have to resist the attraction of better pay and someone else closing the sales once the business is up and running.