8 ms·
One year of Rust
- grenoire 11y agoOne year since stable? It feels like five years for the level of maturity they have achieved.
- deutronium 11y agoI was confused by that, apparently it's one year since the first stable release.
- merb 11y agoExcept the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
- nemaar 11y agoWith this speed of development, I'm pretty sure it is coming.
- merb 11y agoactually idea-rust made great progress, yes.
- jonesetc 11y agoI'd say the tooling is pretty great only with the exception of an IDE. Debugging, building, testing, packaging all seems pretty well handled.
- merb 11y agopackaging will work great if you don't rely on any unicorn library that will put their dylib/so files in some ugly path's that aren't standard. (FFI only) actually not the worst thing for most people, but linking against a paid library will mostly end up with setting LD_LIBRARY_PATH at some point.
- krisdol 11y agoA big pain is still JIT compilation. Last time I used rust, even small changes to code required a full re-compilation.
- steveklabnik 11y agoTo be clear: Rust doesn't have a JIT. But we've been doing a lot of work on incremental recompilation, which will fix this problem. (Or rather, we've been working on the precursor requirement, MIR.) To be extra clear, a crate is the unit of compilation in Rust, so changing your code means that the whole crate it's in needs recompiled; your dependencies won't be. Or, if your project is split up into multiple crates, the other ones won't. Incremental recompilation will reduce this level of granularity such that the whole crate won't need to be recompiled.
- matthewmacleod 11y agoAre you sure you mean JIT rather than incremental compilation? The former is a pretty different concept that AFAIK Rust has no implementation of. I think we are likely to see better incremental support with the recent development of MIR, but I'm not sure what the current plans are. Should help tooling around the language generally!
- krisdol 11y agoYou are correct. I doubted JIT was the right word at the time but couldn't think of the right term. Incremental support is what I mean.
- msbarnett 11y ago> Debugging, building, testing, packaging all seems pretty well handled. Eh, debugging is a mess, at least on OS X. Rust advertises LLDB support, but it seems semi-broken. Listing source is non-functional and just setting a break-point requires a lot of hand-holding.
- pcwalton 11y agoBug reports of specific problems would be very appreciated! We emit fairly complete DWARF, but debuggers tend to be finicky about the exact subset of DWARF they accept.
- msbarnett 11y agoI'll try to submit a report later. It's exactly what it sounds like, though. $ cat hello.rs fn main() { println!("Hello world!"); } $ lldb -v lldb-350.0.21.9 $ uname -a Darwin mycomp 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64 $ rustc --version rustc 1.8.0 $ rustc -g hello.rs $ ./hello Hello world! $ lldb hello (lldb) target create "hello" Current executable set to 'hello' (x86_64). (lldb) source list (lldb) (lldb) b 2 error: No selected frame to use to find the default file. error: No file supplied and no default file available. I don't see how the core team could be unaware of this unless literally no one has done even a cursory glance at OS X & LLDB in months.
- pcwalton 11y agoWell, I do use it regularly for testing Servo. There's a debugger harness run as part of the test suite too. (Not to say we shouldn't fix whatever is causing your problem, though!)
- msbarnett 11y agoI can make it work if I feed full file paths to the debugger using syntax I can't remember off the top of my head. Maybe that's one way some scripts might be functioning? I'll copy and past this into a Github issue when I have a sec. edit: https://github.com/rust-lang/rust/issues/33674 https://github.com/rust-lang/rust/issues/33674
- blakeyrat 11y agoOk, maybe I've been too spoiled by Visual Studio, but debugging without an IDE? That sounds extremely painful to me.
- sargun 11y agoI really wish that Jetbrains had a Rust IDE. I love their Go, and Erlang plugins for IntelliJ, Java with IntelliJ, and Clion with C. Without them, I don't think I could be anywhere as effective as I am. I tried to pickup Rust, but I was super frustrated by the code/compile/run cycle with the current plugin. But, hopefully more users will make that better.
- grenoire 11y agoJetbrains Rust IDE would genuinely make Rust my go-to language for pretty much every task I can think of.
- PascalW 11y agoCouldn't agree more! There's some work ongoing on a third party Rust plugin for InteliJ but it still has a long way to come.
- deleted 11y ago[deleted]
- EugeneOZ 11y agoThere is unofficial plugin: https://github.com/intellij-rust/intellij-rust https://github.com/intellij-rust/intellij-rust and works very well: https://www.youtube.com/watch?v=mHa7QlFz7io https://www.youtube.com/watch?v=mHa7QlFz7io (small video recorded by me)
- jdright 11y agoIs that Racer happening? It look like there is still a lag in the completion suggestion... and that is a huge problem (mainly when using it as to find things).
- EugeneOZ 11y agoNo, this plugin works without Racer. I use it every day and I don't see any problems with code completion. Except of cases where code completion isn't supported yet :) But it's all personal and better to try - it's free. To clarify: I'm not author of this plugin. And I tried Racer with Microsoft Visual Code plugin - it works without any lags, very fast. Just fails sometimes :)
- AsyncAwait 11y agoNot as great as a full IDE, but Atom.io + tokamak(https://vertexclique.github.io/tokamak https://vertexclique.github.io/tokamak) + atom-ctags(https://atom.io/packages/atom-ctags https://atom.io/packages/atom-ctags) get you a decent editor/light IDE setup. I agree however that it would be nice to have ie lifetimes visualized and stuff like that, hopefully sometime soon...
- josteink 11y ago> Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. I just found this link[1] for a pretty complete Emacs IDE-like setup the other day. I'm not a Rust programmer, but it seemed promising enough that it made me want to give it a spin. [1] http://julienblanchard.com/2016/fancy-rust-development-with-emacs/ http://julienblanchard.com/2016/fancy-rust-development-with-...
- shmerl 11y agoI'm not into IDEs, so that doesn't bother me. But by tooling I'd understand cargo. It is improving.
- tracker1 11y agoReplied in the wrong child.... May want to give VS Code + RustyCode[1] extensions a look. [1] https://github.com/saviorisdead/RustyCode https://github.com/saviorisdead/RustyCode
- vvanders 11y agoI actually find the tooling to be quite decent. VSCode + Racer has worked pretty well for me so far.
- Lewisham 11y agoI'd say rustdoc is pretty rough. It's very hard to navigate the rust stdlib vs, say, Go, and when you do find what you want, it's often specified in some very cryptic manner that seems to require a PL PhD. It is a really big barrier to adoption because it's very hard to find out what functionality is or is not offered. Here's an example: I want to iterate over a set. Easy, right? No. http://static.rust-lang.org/doc/master/std/collections/hash_set/struct.IntoIter.html http://static.rust-lang.org/doc/master/std/collections/hash_... Look at the signature for Cycle. It's really hard to know what this does even though it's trivial: fn cycle(self) -> Cycle<Self> where Self: Clone When you click through to the real documentation, it describes a useful use case for this. But that's not how programmers think. They think "I need to do X right now so I'll find something that looks right" not "I'm going to click through the documentation... oh X looks interesting I'll remember that later". There's no way to infer what Cycle really does without having actually clicked through or used it.
- pcwalton 11y ago> fn cycle(self) -> Cycle<Self> where Self: Clone I agree that a summary would be good, but this doesn't require a PL Ph.D. It means "cycle is a method that moves its receiver and returns a Cycle object of the same type of the receiver, and only works if the receiver is cloneable". The trickiest thing here, IMHO, is move semantics, which is something fundamental to Rust in general.
- vvanders 11y agoYup, I've got the same feeling here. If you've spent more than a cursory time with Rust this is pretty straightforward. You'd represent this in Java(minus move semantics, because Java has nothing like that) via: class IntoIter { public Cycle<T extends Clone> { ... } ... } Where Clone is just an interface that knows how to clone its value.
- Lewisham 11y agoFair enough; some more noodling over the signature made it a bit more obvious than it seemed banged out at the back of an OSCON presentation. I think the point still holds. Maybe just not for that one.
- quarterto 11y agoWell, it has been around for about that long. The "one year" is since the stable release 1.0.
- grenoire 11y agoI meant since the stable release in fact.
- steveklabnik 11y agoRust has been in development for almost a decade at this point; but the language changed significantly many times before 1.0. It's been one year since the 1.0 release, which is the language we know today as "Rust". All those older languages are dead and gone now. I'm actually doing a talk about the ACM's Applicative conference in NYC this year talking about the history of Rust.
- jandrese 11y agoThis is one thing that's a little annoying to me. I know if I develop a Rust app today I can't leave it alone or it will decay horribly.
- steveklabnik 11y agoThat should not be true. 1.0 meant that we stopped breaking things on a daily basis, if your code runs on stable today, it should run on stable tomorrow, modulo any soundness fixes (of which we have had two or three this year, which were all trivial to update). If it is true, please file bugs. We do our best not to break people's stuff, going to pretty extreme lengths compared to many other ecosystems.
- kzrdude 11y agoand occasional other breaking compiler bug fixes that are not really soundness fixes.
- pcwalton 11y ago> This is one thing that's a little annoying to me. I know if I develop a Rust app today I can't leave it alone or it will decay horribly. No, it won't. Rust has been stable since 1.0, as the article itself mentions.
- tatterdemalion 11y agoGood news for you: this is a complete misconception. Rust has been stable for a year. With a minor caveat for actual bugs in the language, your code will compile on all Rust 1.X compilers from now until the end of time. Upgrading Rust versions has been a breeze.
- diminish 11y agoHey HN, do you knoe Any notable projects or startups using Rust? Web, desktop apps, scientific or algorithmic computing etc?
- azdle 11y agoThey've actually been collecting a list of companies using Rust in production: https://www.rust-lang.org/friends.html https://www.rust-lang.org/friends.html (It's also mentioned in the post.)
- mevile 11y agoThe most notable Rust project I know of is servo, the browser written in Rust. https://github.com/servo/servo https://github.com/servo/servo It is a massive undertaking and it's already sort of working in many regards.
- Yuioup 11y agoTFA mentions a couple of projects.
- kibwen 11y agoSee https://www.rust-lang.org/friends.html https://www.rust-lang.org/friends.html for a list of companies using Rust (perhaps most notably Dropbox and Mozilla), but here are some non-corporate projects off the top of my head: Panopticon, a cross-platform disassembler: https://panopticon.re/ https://panopticon.re/ Redox, an everything-is-a-URL microkernel OS: http://www.redox-os.org/ http://www.redox-os.org/ Piston, a modular collection of libraries for game development: http://www.piston.rs/ http://www.piston.rs/ Pijul, a next-gen implementation of Darcs: http://pijul.org/ http://pijul.org/ Xi, a high-performance text editor: https://github.com/google/xi-editor https://github.com/google/xi-editor timely-dataflow, "a low-latency cyclic dataflow computational model" (i.e. big data shenanigans): https://github.com/frankmcsherry/timely-dataflow https://github.com/frankmcsherry/timely-dataflow
- geofft 11y agoDropbox is using Rust for file storage: https://news.ycombinator.com/item?id=11283538 https://news.ycombinator.com/item?id=11283538 http://www.wired.com/2016/03/epic-story-dropboxs-exodus-amazon-cloud-empire/ http://www.wired.com/2016/03/epic-story-dropboxs-exodus-amaz...
- _redwire 11y agoOne thing I'm really hoping to see happen in Rust is more development to make it more "functional," as in suitable for a functional programming style. It's already so close and, while I don't want to bring up the higher-kinded types discussion, things like stronger support for closures being returned from functions are just not quite there yet for me. I filled out the survey that was sent around and mentioned some of my concerns about missing crypto-in-Rust code and some of the shortcomings of the documentation. I'm pretty happy I'm not the only one mentioning one or both of those things, because it makes me hopeful that we'll see improvements soon. In particular, regarding docs, I've found it rather difficult to go from reading a type signature and brief explanation of a function/method and being able to actually use it, as a beginner. For example, when I tried to figure out Hyper, it took me a long time to realize I could use pattern matching in my function signatures to capture a mutable reference to something that Hyper was giving me ownership over. I feel silly having missed that, but being a beginner just referencing the Hyper docs, I really struggled. Does anyone have more information about the crypto situation? In particular, I use ECDSA 384-bit for a lot of the code I write at work and have only been able to find the Ring library, which doesn't seem to feature signing yet. If I could get some high-quality, audited crypto code (or heck, even just some nice Rusty wrappers), I'd be so close to ready to use Rust at my day job and for more personal stuff as well.
- nilved 11y agoI think this ship sailed when Rust removed function purity. Rust is a Scala, not a Haskell.
- _redwire 11y agoSo I'm actually not super familiar with Scala. I do know Haskell a little bit. Could you elaborate on what you think the implications are for Rust's development down the functional route are? I've heard about the potential for support for higher-kinded types, which makes me think there could actually be a strong incentive to be able to do more functional programming in Rust if people started working on monad implementations and such.
- aleksi 11y ago> While much of Dropbox’s back-end infrastructure is historically written in Go I'm sorry, but much of Dropbox’s back-end infrastructure is historically written in Python, not Go. Go is a new addition to the stack. Only a small and very specific part of Dropbox is written in Rust, where things like an effectiveness of CPU caches becomes important. Other back-end code is still being written in Go.
- steveklabnik 11y agoI think it depends on what you mean by "historically". My understanding is that the server-side was largely in go for a long time now, but you're also right that before that, it was Python. While you're right that it's a small and specific part, it's also the core of the whole thing, so it's a very significant part. Dropbox isn't moving away from Go generally any time soon, as far as I know: it's still very much the default.
- aleksi 11y ago> server-side was largely in go for a long time now I guess I call "a new" what you call "a long time now". Dropbox is using Go for about 3 years.
- steveklabnik 11y agoYeah, maybe that's entirely it. Words are tough. :)
- zyngaro 11y agoSo Dropbox is no longer using Python for it's backend code ?
- jamescun 11y agoYeah, this extract does feel a little out of place and almost like a dig at Go. I'm sure it is not but a little clarification wouldn't go amiss. To my knowledge Dropbox's backend is migrating (slowly) from Python to Go (new default), with Rust for some specialist features where the memory management model is preferable.
- lossolo 11y agoI've tried to learn Rust twice because i think it's great idea (memory safety with C++ performance) BUT... Rust seems even more complicated than C++ for me, really i find C++11/14 a lot easier to reason about than Rust. I am not sold on functional programming also. Dangling pointers/memory leaks are problems of C and old C++ but not modern C++. I don't remember when i last seen any memory problems in modern c++ code base where ownership is encapsulated inside smart pointers. I think Rust is great and would have a lot more attention and adoption if version 1.0 would ship in 2009. I think Rust is too late into the game. That's why probably only mozilla is really using it and dropbox for really small part of their infrastructure from known players. From what i researched big part of "friends" that use Rust in production are using it because of hype? I am not sure exactly why but some of their use cases for sure not need systems programming language. Maybe it will not end up like D which tried to solve similar problem. EDIT: It's funny how people down vote my personal feelings about the language without any anti-argument or comment. It seems having other opinion than "Rust is GREAT" is not desirable here.
- Rusky 11y agoProbably getting downvoted because the assertion that modern C++ solves memory leaks is getting kind of tired as far as Rust discussions go, and is also missing the point. Rust doesn't solve memory leaks, it solves memory unsafety- things like use-after-free and iterator invalidation that modern C++ does virtually nothing to help with, and that vulnerability statistics show are still huge problems with programs written in C++.
- dbaupp 11y agoI wrote something on the memory leak vs. memory unsafety confusion a while ago, for those interested in exploring it more: http://huonw.github.io/blog/2016/04/memory-leaks-are-memory-safe/ http://huonw.github.io/blog/2016/04/memory-leaks-are-memory-...
- lossolo 11y agoI don't see usage of new/free without encapsulation, this is not modern c++ which invalidates your point. Using naked new/free is depreciated in modern c++ and is problem of C not modern C++. What kind of statistics? Can you give any links that support what you wrote? All memory leaks/buffer overflows that i saw lately are associated with C (openssl, libc etc) not with C++. For iterator invalidation there are couple of simple rules to remember or for example you can use std::insert_iterator that will not be invalidated even if relocation occurs. You could use static analyzer and would avoid most of the problems. EDIT: My point is that i have nothing to gain from rust when knowing c++ and memory management rules + i got good static analyzer. But probably for someone that do not know C++ at all Rust could be a better choice.