It is kinda unfair to compare the time of writing a service in go and rust if your team already work with JavaScript.
Go was designed to be extremely simple (simplicistic, if you want to be ugly with terms) while rust was designed with very different goals in mind.
Moreover the mental model of JavaScript is much closer to the one of go than the one of Rust.
If you are learning rust and you are not from C/C++ or similar low level languages you are basically re-learning how computers works. Usually on go you don't really care of the difference between the stack and the heap, in rust you have to.
Said so, it is really true that rust has a steep learning curve, however once you get over it the productivity is at least as high as go especially in the long term.
For one off script of ~100 lines I would pick go as well.
Go was designed to be extremely simple (simplicistic, if you want to be ugly with terms) while rust was designed with very different goals in mind.
Moreover the mental model of JavaScript is much closer to the one of go than the one of Rust.
If you are learning rust and you are not from C/C++ or similar low level languages you are basically re-learning how computers works. Usually on go you don't really care of the difference between the stack and the heap, in rust you have to.
Said so, it is really true that rust has a steep learning curve, however once you get over it the productivity is at least as high as go especially in the long term.
For one off script of ~100 lines I would pick go as well.