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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

2017 Rust Roadmap

332 点作者 muizelaar超过 8 年前

22 条评论

cheepin超过 8 年前
I read through the Rust book, and the problem I was having with it and the other docs is that it was hard to map the Rust concepts with what actually runs when it is compiled. For a language that touts &quot;uncompromising performance&quot;, it was difficult for me to find performance characteristics of the underlying abstractions and std library (for example, are algebraic data structures just tagged unions or does the compiler do more fancy things with them? What about iterators?). I&#x27;d really like to see a &quot;Rust for C&#x2F;C++ devs&quot; guide that helps you figure out if you were using [some C++ feature] the way to get that behavior&#x2F;performance with idiomatic Rust.<p>Another thing that is still tricky for me is figuring out when I should use &#x27;unsafe&#x27; blocks in my code. Is it to be avoided if at all possible, or should I go there any time the &#x27;safe&#x27; part of the language is making it difficult to express what I want? The meme that Rust is C++ without SegFaults and or race conditions is a bit misleading since the actual guarantee is that you don&#x27;t get SegFaults or Race conditions outside of Unsafe blocks, and any nontrivial project will make use of unsafe blocks.
评论 #12767007 未加载
评论 #12766609 未加载
评论 #12766653 未加载
评论 #12766572 未加载
评论 #12766803 未加载
评论 #12768131 未加载
评论 #12771433 未加载
评论 #12767316 未加载
adamnemecek超过 8 年前
I would also suggest taking a page out of Apple&#x27;s playbook and providing some official sample apps like <a href="https:&#x2F;&#x2F;developer.apple.com&#x2F;library&#x2F;content&#x2F;navigation&#x2F;#section=Resource%20Types&amp;topic=Sample%20Code" rel="nofollow">https:&#x2F;&#x2F;developer.apple.com&#x2F;library&#x2F;content&#x2F;navigation&#x2F;#sect...</a>. Reading the books is one thing, but seeing the patterns actually used is another. You don&#x27;t need as many as Apple, only a couple really, but make sure they are well written and straddle a couple of use cases. And like go crazy with the idioms, I want to see the most idiomatic Rust code.<p>When learning a new platform, it&#x27;s always frustrating having to hunt for good code. I actually find these similarly important as docs (maybe even more because I tend to reference good open source for much longer than docs).
评论 #12766424 未加载
评论 #12766671 未加载
joshmarlow超过 8 年前
I would love to see Rust with a REPL. I use Python professionally a lot and have done a fair amount of OCaml in my spare time and both have excellent REPls in the form of `ipython` and `coretop`. Quick experiments <i>with auto-complete</i> is incredibly helpful for exploring a language. That&#x27;s the only thing I really miss from those languages; when I want to wrap my head around a bit of syntax or a library feature in Rust, I build out a quick little experiment and see if it compiles and behaves as I expect it. With a good enough REPL, that&#x27;s unneeded.
评论 #12766639 未加载
评论 #12768371 未加载
评论 #12767296 未加载
评论 #12766616 未加载
评论 #12766827 未加载
评论 #12767162 未加载
评论 #12772470 未加载
评论 #12767673 未加载
dikaiosune超过 8 年前
It&#x27;s important to note that this is an RFC which has been proposed, and there&#x27;s likely to be a good deal of discussion and revision before it&#x27;s merged&#x2F;adopted as the official 2017 roadmap.<p>The conversation can be followed&#x2F;joined&#x2F;whatever here: <a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;pull&#x2F;1774" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;pull&#x2F;1774</a>
评论 #12769473 未加载
leshow超过 8 年前
Awesome. I have used Iron a few times to write small web services, but I can&#x27;t wait for Rust to really have a strong story for the backend. If that happens it&#x27;ll be the first language I reach for whenever I need to write a backend.<p>I think it has a lot of great bonuses already. It&#x27;s language ergonomics are that of a high-level language, yet it is extremely fast, and I can be very confident in my code if it compiles.<p>Rust is one of my favorite languages, keep up the great work guys.
评论 #12766923 未加载
评论 #12767071 未加载
评论 #12769311 未加载
fixxer超过 8 年前
Awesome to see the learning curve addressed with such high priority.<p>I like Rust and I&#x27;d like to use it more, but I generally lean on Go or C for writing anything that needs performance. I can&#x27;t quite get past the awkward, fumbling stage with Rust. Go, on the other hand, was really easy to get acquainted with and not too substantial of an effort to get to strong expertise. I&#x27;ve been able to teach Go to junior devs with no background and hand off projects within a couple weeks. Rust is awesome, but fits in a very different bracket IMO.
评论 #12766461 未加载
评论 #12766479 未加载
cm3超过 8 年前
&gt; Rust should integrate easily with C++ code<p>The day that Rust manages to have always up to date Qt bindings that do not force you to make compromises compared to the C++ API, I think the C++ support will be at a comfortable level. Right now there are fresh efforts in the Rust and Haskell camps to solve this cleanly in a modern way. It would certainly help if the consumption of C++ APIs via llvm (which is used a lot byt Rust) was made a first class feature like you can import and export C APIs. Exporting C++ classes is a whole different story and may not map in any reasonable way to Rust modules or crates.
评论 #12766686 未加载
rjammala超过 8 年前
One way to improve productivity of Rust with respect to the learning curve is to add more screencasts&#x2F;tutorials to <a href="http:&#x2F;&#x2F;intorust.com" rel="nofollow">http:&#x2F;&#x2F;intorust.com</a><p>I found the existing ones very helpful and instructive.
评论 #12767081 未加载
kalmar超过 8 年前
This is a better link, as it will include the discussion: <a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;pull&#x2F;1774" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;pull&#x2F;1774</a>
EugeneOZ超过 8 年前
&gt; Rust should provide a solid, but basic IDE experience<p>After using IntelliJ IDEA plugin [1] (works in free community version too), I don&#x27;t understand what else people need :) Plugin is pretty powerful. Also Racer works great in VS Code and other editors.<p>&gt; Rust should have a lower learning curve<p>Rust is easy enough to learn, the only issue is a steep start. After couple of months everything is not harder than JS and smart compiler actually makes me more and more lazy :) So I think only thing we need is books&#x2F;articles to help people switch from other languages, to help them overstep initial difficulties.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;intellij-rust&#x2F;intellij-rust" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;intellij-rust&#x2F;intellij-rust</a>
ifhs超过 8 年前
It&#x27;s amazing how much the rust team has nailed it. they know exactly what the problems are. I do not know of any other team as talented as rust. Then language is also quiet brilliant. I have started rewriting all my code in rust the days. It just makes sense.
gravypod超过 8 年前
&gt; 1 in 19: lack of IDEs (1 in 4 non-users)<p>I expected that to be higher actually, but that&#x27;s still the only reason I don&#x27;t use the language. I&#x27;ve come to rely heavily on IDEs. Whether right or not it&#x27;s a huge factor in my decision to wait for the language.
评论 #12767528 未加载
评论 #12766934 未加载
评论 #12769114 未加载
unfamiliar超过 8 年前
&gt;We asked both current and potential users what most stands in the way of their using Rust, and got some pretty clear answers:<p>&gt;1 in 4: learning curve<p>&gt;1 in 7: lack of libraries<p>&gt;1 in 9: general “maturity” concerns<p>&gt;1 in 19: lack of IDEs (1 in 4 non-users)<p>&gt;1 in 20: compiler performance<p>&gt;None of these obstacles is directly about the core language or std; people are generally happy with what the language offers today. Instead, the connecting theme is productivity—how quickly can I start writing real code? bring up a team? prototype and iterate? debug my code? And so on.<p>I don&#x27;t really see how this conclusion was reached from that data. The &quot;learning curve&quot; is almost certainly a reflection of the language being a little esoteric and the demands of the borrow checker. And &quot;lack of libraries&quot; is partly a comment on the ecosystem, but also partly shows that std is obviously lacking for some needs. Finally, &quot;general maturity concerns&quot; refers to worries that the language or std will keep changing, as is assumed they have not been perfected yet.<p>Those are the top 3 concerns and to me, both seem to relate directly to the language or standard library.
评论 #12768888 未加载
评论 #12768927 未加载
geodel超过 8 年前
Overall it looks good.<p>When I look at this :<p>&quot;Production use measures our design success; it&#x27;s the ultimate reality check. Rust takes a unique stance on a number of tradeoffs, which we believe to position it well for writing fast and reliable software. The real test of those beliefs is people using Rust to build large, production systems, on which they&#x27;re betting time and money.&quot;<p>I see a little bit of haste towards production use. From &#x27;Rust 1.0 is out just last year&#x27; to &#x27;We really need successful production use&#x27;, It does some to be a push from management to justify continued investment in Rust project.
评论 #12766739 未加载
评论 #12766672 未加载
评论 #12766676 未加载
dj-wonk超过 8 年前
Re: &quot;Here are some strategies we might take to lower the learning curve: ... Improved docs. While the existing Rust book has been successful, we&#x27;ve learned a lot about teaching Rust, and there&#x27;s a rewrite in the works. The effort is laser-focused on the key areas that trip people up today (ownership, modules, strings, errors).&quot;<p>Yes, please. I get better every day with Rust. I&#x27;d ask that the docs on lifetimes be improved with more elaboration on the ideas and more examples. Frankly, I still find the details confusing, so I can&#x27;t offer more particulars right now.
agentgt超过 8 年前
For what it&#x27;s worth I hope serde or whatever default serializers are improved. I had some serious issues trying to combine libraries because of serde changing too much. Albeit this was about a year ago so it probably is fixed.<p>Second it would be nice to see some best practices not just for libraries but application development. What to do and what not to do. Maybe a cookbook or even... design patterns. I had a hard time trying to figure out if I should embrace closures or go traits (at the time closures were not working as well so maybe this is not an issue either).
评论 #12768467 未加载
coherentpony超过 8 年前
I&#x27;d also like to see a push towards applications in scientific computing.
评论 #12766864 未加载
评论 #12766507 未加载
zzzcpan超过 8 年前
Focus on high-performance servers, async I&#x2F;O, C integration is very promising. These are Go&#x27;s weak points, could become a good alternative and a direct competition for Go.
评论 #12767039 未加载
评论 #12766586 未加载
sotojuan超过 8 年前
Really nice! I try to learn as little languages at the same time as possible so sadly I have no time for Rust at the moment, but it looks like it&#x27;ll only get better.
Dowwie超过 8 年前
Idiomatic Rust guides would be very helpful
petters超过 8 年前
My personal code base is C++&#x2F;cmake and Python.<p>It would be really nice with a way to slowly start writing code in Rust instead.
评论 #12768787 未加载
serge2k超过 8 年前
&gt; Rust should have a lower learning curve Rust should have a pleasant edit-compile-debug cycle Rust should provide a solid, but basic IDE experience<p>I know the list isn&#x27;t necessarily prioritized, but these 3 feel backwards.<p>A good IDE will provide can help facilitate easier edit&#x2F;compile&#x2F;debug cycle which makes learning the language faster because it&#x27;s cheaper (time wise) to figure things out.
评论 #12768729 未加载