You are comparing a (the most?) featureful web framework to a vanilla http server.. of course one will be significantly more resource heavy.
reply> using SpringBoot
replywell there's your answer, isn't it?
I cant really agree on Rust. It does take a bit more time to write the same code in rust vs go. But in my experience the code is much more likely to be incorrect in go than it is in rust. Which over longer periods means rust is easier to maintain.
replyOn the other hand, most pieces of software in this world are kind of mediocre code written by unmotivated employees within tight timelines.
replyIn such context, I think Go might be a better or at least, more realistic, compromise in most cases.
If you have unmotivated employees then using Go will only exacerbate the shortcomings it has. Cutting corners is much easier in Go than it is in Rust. But in general it's true, if you want a piece of code released a bit faster but spend more in developer hours maintaining it later than Go is the better fit. And there are definitely use cases for that.
replyYou can write exploratory code in Rust fairly quickly, it's just obvious when you've done so due to the heavy boilerplate involved. Keep in mind that the earliest versions of Rust were actually very Golang-like, the language iteratively evolved towards what it is today.
replyThis article convinced me to switch from Go to Rust: https://discord.com/blog/why-discord-is-switching-from-go-to...
replyThe issues with Go in that article only surfaced at Discord scale.
replyI'm not sure the effort part makes sense now that we have LLMs? LLMs basically liberate language choice, which has made Rust incredibly attractive to me since I basically get good performance out of the box, while any possibly annoying pedantic obsession with correctness can be easily handed over to the LLM.
replyIf I use a JVM language, running my test suite takes 10 to 30 seconds. With Rust it spends 3 seconds compiling and half a second to run 250 tests.
The irritating parts of Rust are more related with bloated libraries like serde that insist on generating code which massively slows down compilation for not much benefit.
> If I use a JVM language, running my test suite takes 10
replySounds like a bad build tool.