TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Recommendations for language when building API?

3 点作者 mr_00ff007 个月前
Hello all,<p>I am building a backend API and I have free reign to choose a language to build it in. I know it will deal with async and I heavily prefer statically typed languages, so those are my two preferences.<p>I work as a C++ programmer but obviously no way I am using that. I am a big fan of Rust, but I know async is painful and why put up with borrow checker when GC is fine.<p>The two I am leaning towards is Go and Kotlin, but very interested in opinions. My experience in either is basically 0

2 条评论

npalli7 个月前
Go for Go, super easy to pickup (relatively speaking), clean deployment and good story on network services and concurrency. Kotlin is ok but only better if you have an existing JVM infrastructure you want to leverage. Otherwise, stick with Golang.<p>Also, congrats on not falling for the hype and going for Rust. Saved yourself a ton of headache.
评论 #42013241 未加载
PaulHoule7 个月前
Java. Async is for the birds, use ordinary threads first and in the p=0.001 case that&#x27;s not good enough use virtual threads. Given all the work that&#x27;s gone into Java since JDK 8 I think the case for Kotlin, Scala and other static JVM languages is weaker than it&#x27;s ever been.