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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

The impossible case of pitching rust in a web dev shop

21 点作者 WilliamHurst超过 2 年前

4 条评论

gorjusborg超过 2 年前
Rust in a web dev shop would be a huge premature optimzation smell for me.<p>Most public web apps are expected to be up pretty much all of the time, which today, means cloud hosting and horizontally scalable architecture. In such a setup, I don&#x27;t see how squeezing every last drop of performance is worth it. When I can just change a number and get more instances, choosing the language with higher cognitive load is going reduce any cost savings due to lower resource usage.<p>Doing something as mundane as writing text to a socket just doesn&#x27;t need to perform all that well. Developer effort costs more than the CPU&#x2F;memory.
评论 #32984411 未加载
xrd超过 2 年前
I keep looking for something really special for writing web applications using rust. Is there something on the horizon? It seems like rust on the server side is an easy decision but I&#x27;m unclear if there is a way rust could replace nodejs as the isomorphic application language on both server and browser.<p>Clojure and ClojureScript was such an interesting way to bring lisp into the browser and seemed really revolutionary. And without really limitations on what you could build. Where is the rust version of that?
评论 #32977578 未加载
brundolf超过 2 年前
The bummer is that the main reasons I would want my company to adopt Rust are 1) the toolchain and 2) the type system (we&#x27;re on Python, which has the worst story imaginable for both of these). But most of the pain in learning and using Rust comes from its performance characteristics, which we mostly don&#x27;t need<p>Such is life
评论 #32980048 未加载
karmakaze超过 2 年前
I would say &quot;the irrelevant case..&quot;<p>Where Rust excels is in safety when using concurrency. Most web apps and APIs have a single thread used per request. I&#x27;ve also used async&#x2F;futures that work fine without ownership modelling.<p>As for performance switching from Ruby&#x2F;Python to Java&#x2F;C#&#x2F;Go will pay off not so much to then go to Rust unless it&#x27;s a particularly high throughput or latency zensitive app in which case you&#x27;d already know it matters.