Formerly using Python, motivated to migrate to a modern stack, and so recently attempted to write a simple web back-end for my apps in Go and then in Elixir. Same logic, same unit tests, two languages.<p>Really liked: the simplicity of Go&#x27;s build, not having to spawn N processes on the server side, the compiler catching so many issues, the very strict formatting rules, all a major win over Python. However, didn&#x27;t like how verbose the code turned out, especially for parsing or any data manipulation tasks. For server-side debugging&#x2F;tools, it&#x27;s also a bit of a build-your-own adventure.<p>Elixir I found to be much more pleasant to write and subsequently read, more well-suited for back-end tasks, great for generating and parsing data. Also, more things in the toolset for back-end deployment, in large part due to the OTP stack.<p>Perhaps Go&#x27;s ideal use case is local system tools, compilers, or anything else that requires concurrency (let&#x27;s say, creating tools like &quot;ls,&quot; or Apache bench, or gcc, or cURL), and something like Elixir is more ideal for building actual servers.