6 ms·
Why we chose Rust
- iampims 7y agoWhy is this on bitbucket.org? I don’t see a link between the author’s post and the bitbucket blog. Is it just “content marketing”?
- nevi-me 7y agoThis post feels like hype marketing or something. They're telling me what I already know/believe about Rust, and it doesn't help that it's a guest post. They're choosing Rust for an embedded usecase, they could have gone into detail about embedded Rust, and whether they consider the ecosystem to be mature/sufficient for their needs. If they didn't consider this (seeing that this feels like a decision made over theoretical discussions and previous benchmarks), this could come back to bite them.
- fwip 7y agoI'm surprised to see that Go wasn't considered. While not as lean and mean as Rust, it also has excellent support for parallelism and safety, while being easier to get into. Edit: For clarity, I'm not saying Go is the best choice. But when Lua, Python, and Java are in the running, it's surprising that Go wasn't. Especially when the article calls out the learning curve of Rust as a downside.
- hackcasual 7y agoIt's for an embedded (SoC) device, so likely they didn't want the overhead of a more managed language.
- dom96 7y agoand yet they include Python in the comparison?
- cyphar 7y agoMicroPython is a wholesale rewrite of Python to be suitable for microcontrollers. From memory, the ESA (European Space Agency) uses it for some of their projects.
- deleted 7y ago[deleted]
- randyrand 7y agoHe never said it was embedded.
- reificator 7y ago> He never said it was embedded. > We needed a language that was fast enough to allow minimum real-time latency and use limited resources of a SoC device.
- flukus 7y agoSoC also describes a modern phone, rasberry pi, probably even some modern laptops/netbooks. I think it's generally agreed that these are not embedded devices, but the line used to be much blurrier. It sounds like the evaluated their options, added in a few that they were never really going to consider anyway, came to the conclusion that C++ was best but then made up some reasons to use rust anyway.
- solipsism 7y agoIt's a real stretch to call Go's support for memory safety "excellent".
- vlovich123 7y ago> minimum real-time latency and use limited resources of a SoC device.
- 0815test 7y agoWell, Go has excellent support for parallelism and excellent support for safety - whereas Rust actually supports parallelism with safety. Rust is also gaining lots of useful "tweaks" that will make it quite a bit easier to get into in the future - and the syntax alone is a big draw to former Ruby, Python etc. programmers, while you really can't say the same about Go. Now, of course Rust is not for everything (some things really can't be done without efficient GC, and Go gives you that), but it looks like these Bitbucket users made a very solid choice here.
- harikb 7y ago> Author bio: Mohit Agrawal is a software developer from Indore, India and works at Oviyum Technologies, an outsourced product development firm Not sure why bitbucket is promoting this particular guest post.
- reificator 7y ago> it looks like the Bitbucket folks made a very solid choice here. Just a heads up, this is not from the bitbucket team. That's just where it's hosted.
- apta 7y ago> has excellent support for parallelism concurrency, not parallelism, and even there it doesn't have anything similar to immutable data structures or java.util.concurrent or System.Collections.Concurrent > support for safety Not more than any other available GC'd languages. > some things really can't be done without efficient GC, and Go gives you that Only if you care about pause times at the expense of throughput, and you don't have to deal with very large heaps
- deleted 7y ago[deleted]
- apta 7y ago> support for parallelism It has support for concurrency, not parallelism. > and safety It's not any safer than other GC'd language available today, and likely quite less so compared to languages with immutability and proper persistent data structures in them (Scala, Java, F#, etc.)
- bsaul 7y agoI’m curious what you mean by « no support for parallelism » ? Goroutines are scheduled on different processors, and do run in parallel.
- apta 7y agoIt's at the discretion of the runtime though. With native threads you have more control. And you can have several goroutines running on the same processor concurrently.
- Waterluvian 7y agoOff topic nitpick: I wish Python stopped being added to these kinds of performance lists. Python isn't a poor tool for those kinds of problems, it's the wrong tool. And I don't mean, "oops you locked yourself into the wrong language." I mean that valid Python is Python that calls into a language like C or Rust when there's performance needs. Numpy and Scipy are, I'm going to bet, mostly C. Imagine I did a comparison of the fastest way to cut a board lengthwise. And my comparison was using a table saw, a jigsaw, a circular saw, and a planer. Actually, that sounds dumb enough that I kind of want to do that. All the worst ways to rip a board.
- cyphar 7y agoMicroPython is a wholesale rewrite of Python to be suitable for microcontrollers. I imagine this is the reason it was included in a comparison for languages to be used for an SoC. From memory, the ESA (European Space Agency) uses it for some of their projects.
- tylerhou 7y ago> Numpy and Scipy are, I'm going to bet, mostly C. You'd be surprised; About 25% of SciPy (much of the numerical computing portions) are in FORTRAN. It turns out that decades of compiler/numerical computing research has made the FORTRAN compiler generate numerical code which runs faster than GCC/Clang today. https://github.com/scipy/scipy https://github.com/scipy/scipy
- cyphar 7y agoMost people use the GCC Fortran front-end. I think the main reason you get speed from Fortran is because it provides more hints to the compiler, but also because generations of PhD students have been optimising compilers for Fortran-specific performance gains.
- pjmlp 7y agoPeople that care about Fortran performance use Intel, PGI, IBM compilers.
- hackcasual 7y agoI don't believe the author works for either Atlassian or on bitbucket, just uses it.
- kaycebasques 7y agoYes, this appears to be a guest blog. The way that HN only exposes the domain of URLs led me to believe that Bitbucket was now using Rust.
- Deimorz 7y agoEven the full url doesn't make it any more clear, it's just https://bitbucket.org/blog/why-rust https://bitbucket.org/blog/why-rust It's strange that Bitbucket is giving urls like that to "guest posts". There's very little distinction from an official post like this one: https://bitbucket.org/blog/take-control-with-branch-restrictions https://bitbucket.org/blog/take-control-with-branch-restrict... It even shows Ash Moosa (an Atlassian employee) as the author of all the guest posts when you're on the main blog page (https://bitbucket.org/blog/ https://bitbucket.org/blog/), and you can only see who the actual author is by going into the post individually and looking for the "guest post by" section at the top of the text (and below another section showing Ash Moosa as the author). Really bad design if they're planning to put up a lot of guest posts like this.
- deleted 7y ago[deleted]
- reificator 7y agoYes, it's very unclear until you click through. This article is not about a team at Atlassian, which is what HN's presentation implied.
- lacker 7y agoRust seems like a fine choice for this use case. However, the decisionmaking process is a bit odd. They considered Java, Lua, and Python, but not Go? I think Go is far more "Rust-like" than those other three, ie for people who want something one notch nicer than C++.
- bluejekyll 7y agoWhile I don’t disagree about the consideration of Go, calling Go Rust-like is really strange. I think of Go as more Java-like than Rust-like. But even that’s a hard comparison. Really, Go is C-like with a garbage collector for memory safety. Rust is Java or C++-like with a strongly typed compiler, support for generics (not Go), lifetimes for memory management and no GC (closer to C++), and a type system that enforces some constraints around concurrency. I guess they are similar in that they both (by default) create static binaries, but so does C and C++ (if you want). Rust and Go seem to get lumped together because they both came on the scene around the same time, but that is pretty much where the comparison ends.
- apta 7y ago> Rust and Go seem to get lumped together because they both came on the scene around the same time That, and that the golang authors at that time claimed that it was a "systems language". They would later go back on that by attempting to redefine what "systems language" meant.
- pjmlp 7y agoHowever Go is indeed being used as real systems language, even if the anti-GC crowd deslikes it. Examples in production, gVisor, Android GPU debugger, Biscuit and other research OSes, tiny GO for embedded targets, compiler development.
- apta 7y agoI'm not anti-GC :) The language itself though doesn't lend itself well to larger complex designs however, which I feel precludes it from more interesting projects, and we can see that by the fact that it's mainly getting used for "devops" kind of work. Compare that to Rust or Java (e.g. GraalVM) or C#, the latter two which weren't really advertised as "systems" languages, yet were used there anyway (maybe real-time Java is something else though)
- lacampbell 7y agoMy big takeaway from the benchmark was that C++ used just over 20% the memory of rust. If you're stressing about performance, that's huge.
- ysleepy 7y agoThats probably just the rust binary being a bit larger, I wonder how the memory measurements are done. Java is suspiciously close to 512MiB which could mean they just looked at the RSS size of the process, but Java does not automatically give memory back to the system, especially if the min heap is set to something like 512M. Java being in the same order of magnitude of performance, they might be abandoning the java ecosystem to quickly considering how good the tooling and library ecosystem maturity is.
- apta 7y ago> but Java does not automatically give memory back to the system It depends on which GC is being used. Newer GC's like Shenandoah and ZGC (as well as G1GC I believe) do. It also seems they didn't look at GraalVM to generate native binaries for Java (e.g. https://quarkus.io https://quarkus.io)
- munificent 7y agoSure, but that benchmark is a single point on a manifold. That point may tell you little about your program which likely differs from the benchmark along several axes.
- lacampbell 7y agoSure, but it the post went "we need a language with great performance, so we chose the second most performant one according to this test.". It was a bit odd.
- 0815test 7y agoThey're just linking to an old blogpost from 2015 there. Back then Rust used to rely on a custom memory allocator which introduced a lot of RAM overhead, this has been fixed for quite some time now. Don't get me wrong, I like that these folks are using Rust, but this post is leaving me with a bit of a weird feeling - it just does not seem very impressive or meaningful.
- sonnyblarney 7y agoIt would be nice if some details could be given about the project so we could put 'performance' etc. into context. There are not that many applications that really need the extra performance boost from the JVM to C++, usually, that would be a platform issue, i.e. the device can't support the JVM or whatever. For smaller projects (we're dealing with sensors, does this mean it's small?) especially hardware related, the issues are going to be integration, libraries, supportability for those tricky things; in such scenarios one's hand is often pushed to C etc.. The advantages of Rust it would seem would have to be rather significant and noteworthy to make the jump to a nonstandard platform, for so many reasons.
- nullbyte 7y agoWait, isn't Bitbucket written in Java though? Are they rewriting it in Rust?
- kunday 7y agoIt seems to be a guest post. The url makes it appear like Atlassian is doing some rust. Which it is not atleast, in this case. Edit: ex-atlassian here. Bitbucket initial implementation was in python when Atlassian bought them in 2011. Not sure what the stack is now.
- dingo_bat 7y agoFor embedded applications such as these, if you're not choosing C++, you're choosing wrong.
- kahlonel 7y agoIf you're gathering data through multiple sensors data from one end, and pushing it out to network from another, the performance of the 4-core ARM CPU should be the least of your concerns. You are never going to reach 100% CPU utilization unless you're doing something very wrong. Contemporary sensor protocols are slow, to say the least. Same for the network end. You'll saturate atleast one of those two ends before running out of CPU power. Use Python. It is easy, fast and has a ton of library support for numerical analysis. Stop buying into the hype please.