I hear what your are saying, but there is some advantage to having the same language in multiple places in the stack. One of the advantages of JavaScript is that it can be used both on the front-end and the server. Some people hate that and insist that "real" programmers use a "real" server language but that is not a reasoned take. There are pragmatic reasons to want the same language across the stack.
And so it sometimes goes the other way. Java was used through a transpiler for the front-end for some of the classic Google apps (I don't know if that is still the case). So it makes some sense, for a Python heavy team, to consider the same approach. And with the growing support of WASM it is probably even easier than it was when it required transpilation to JavaScript. And since a lot of ML work is in Python there is undoubtedly growing interest.
Comments
I hear what your are saying, but there is some advantage to having the same language in multiple places in the stack. One of the advantages of JavaScript is that it can be used both on the front-end and the server. Some people hate that and insist that "real" programmers use a "real" server language but that is not a reasoned take. There are pragmatic reasons to want the same language across the stack.
And so it sometimes goes the other way. Java was used through a transpiler for the front-end for some of the classic Google apps (I don't know if that is still the case). So it makes some sense, for a Python heavy team, to consider the same approach. And with the growing support of WASM it is probably even easier than it was when it required transpilation to JavaScript. And since a lot of ML work is in Python there is undoubtedly growing interest.