Languages do matter.

And I think the only sensible backend languages when starting a new for-profit project is Python, Go, and Rust for 99% use-cases.

In other cases, third-party packages, tooling, integrations, and telemetry starts to suffer.

▲

bel8 4 hours ago | parent | next [-]

I think Odin's batteries included approach have a chance to achieve escape velocity.

Specially if their community and their BDFL continues to be welcoming and fun to interact with.

Their 1.0 roadmap announcement is cool: https://youtu.be/dLPAqXi9In0

Here's most of the language in a single demo file: https://odin-lang.org/docs/demo/

▲

coldtea 4 hours ago | parent | prev | next [-]

Keeping it to the most mainstream, Java is a mighty fine choice as well, with even better options for third-party packages, tooling, integrations, and telemetry than most of the above.

▲

well_ackshually 4 hours ago | parent | prev [-]

Forgetting the JVM when it provides absurdly good performance and more packages than pretty much all three of these languages combined is certainly a choice. Even Java and all its verbosity gets fixed by not having to write it manually. Kotlin is also a very viable option. Scala if you're a bit crazy.

	▲	rafterydj an hour ago \| parent [-]
		Most of the people I've encountered that use Java are working on enterprise codebases that are a couple decades old at this point. And I'm totally unfamiliar, but I thought Kotlin was vaguely "Java for Android" - other than existing packages, are there other reasons to choose languages focused on the JVM?