That is utterly untrue. Compare e.g. the terse, intuitive GUI tooling you get with Racket vs. the effort required to achieve an inferior result with Javascript and the framework of the week.
You need to hire a dev that actually knows Racket. Companies already have JS programmers around because they always need to build a front end.
Just compare mobile to desktop. Apps abound in mobile because the extra performance inefficiency actually matters enough that it's worthwhile to put in the engineering effort; on desktop the web app is feature-rich and fast enough.
There's a reason people use FB in a browser on desktop but the app on mobile.
I don't mean performance inefficiency, I mean that developing apps in JS is harder and slower than with other frameworks. I picked on Racket because it's possible to build a cross platform GUI app skeleton in less than a screen full of code, with no external dependencies.
