News for hackers. Stuff that matters.
Re:Trying Rust for web services by dkhenry on Thursday October 01, 2015 @10:19AM (#10311304)
I have fully switched over to Rust to do my web backend's. I use Nickel.rs and it has worked great. The code is very succinct and fast. The only downside I have found to this is that there is no "Hot Reload" which I had with Flask(Python) and Play(Scala).

As the ecosystem grows I only expect it to get better.

Re:Trying Rust for web services by untothebreach on Thursday October 01, 2015 @10:58AM (#10311558)
Unless you are on windows, you can try cargo-watch[1] to re-compile and run your code when the source changes.

1: https://github.com/passcod/cargo-watch

Re:Trying Rust for web services by dkhenry on Thursday October 01, 2015 @11:46AM (#10311958)
I will have to give that a try. Its amazing how much hot reloading speeds up development.
Re:Trying Rust for web services by mixmastamyk on Thursday October 01, 2015 @01:57PM (#10313106)

    sudo apt-get install inotify-tools
and a short shell script.
Re:Trying Rust for web services by zatkin on Thursday October 01, 2015 @10:20AM (#10311309)
Nickle.rs is at http://nickel.rs/
Re:Trying Rust for web services by shepmaster on Thursday October 01, 2015 @11:03AM (#10311605)
It's also spelled "Nickel.rs", as shown in the link ^_^
Re:Trying Rust for web services by zatkin on Thursday October 01, 2015 @11:12PM (#10316504)
Oops, my mistake.
Re:Trying Rust for web services by markus2012 on Thursday October 01, 2015 @04:03PM (#10314239)
I have also switched to Rust for backend work.

I'm using Iron instead of Nickel. Not sure who will become more popular over time...

Because of the language (no null, bounds checking, option/result types, etc.) and borrow checker I find I rarely have to 'hot reload' or even test my code. I realize that sounds surprising. I'm not doing any HTML templating in Rust - that's better done in JavaScript on the client - so I don't have the edit/compile/test cycle for every tweak to the UI.

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @11:22AM (#10311765)
What was behind your decision to pick Rust? My understanding is that Rust is meant as replacement for C++ in places where C++ performance is needed (browsers, systems programming (maybe)), etc. A web server does not fall into that category, so why did you pick it?
Re:Trying Rust for web services by jerf on Thursday October 01, 2015 @11:28AM (#10311804)
"A web server does not fall into that category, so why did you pick it?"

That's too categorical a statement. It depends on a lot of things. Sure, there's a place in the world for PHP pages that take two or three full seconds to render, but it doesn't matter because they're doing something useful and don't get hit a thousand times per second. There's also a place for things that render in under a millisecond because they're getting hit at an incredible rate, and if they also have some sort of interdependencies then Rust can make a lot of sense.

Plus as I've said before, the whole "you're stuck in IO anyhow so who cares how fast the render code runs" dogma has sometimes gone too far. (I know you didn't say anything about that, but I'm guessing based on experience it's what lies behind your point.) My experience in switching from slow languages to fast languages, even doing the same IO, is that you do tend to see real performance gains unless your page was absolutely trivial. Slow languages really are slow in practice.

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @01:34PM (#10312915)
> That's too categorical a statement. It depends on a lot of things.

I didn't mean it to be. Of course there are extreme cases where GC pauses are unacceptable on a web server, but those are relatively rare. Even Google mostly uses Java (although they are heavy C++ users, is it for their web servers?).

There are always extreme cases, which is why I asked the question.

> My experience in switching from slow languages to fast languages, even doing the same IO, is that you do tend to see real performance gains unless your page was absolutely trivial. Slow languages really are slow in practice.

Slow vs. fast is not black and white. Is Go slow? Is Lua slow? I Java (on a warmed up JVM) slow?

We're talking about GC vs. non-GC languages here. Do you really see a difference in performance gains?

Re:Trying Rust for web services by acconsta on Thursday October 01, 2015 @02:30PM (#10313454)
>Even Google mostly uses Java

I'm not so sure about that. The core services (e.g. Search, Maps, Earth, Big table, Map reduce) seem to be C++. Ads is possibly an exception.

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @02:40PM (#10313547)
We're talking specifically about the web application servers here. I wouldn't be surprised that something like Search is C++, it's one of the most visited pages in the world. But I haven't heard specifically that it is.

I don't think it's any secret that Java is huge Java users. If not web servers, then for what?

Re:Trying Rust for web services by acconsta on Thursday October 01, 2015 @03:07PM (#10313773)
50% C++, 25% Java

http://qr.ae/RP7wXh

At Google's scale, the performance difference between Java and C++ can means millions of dollars in electricity alone.

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @03:24PM (#10313955)
That's the amount of code in their repo which covers a lot more than web application servers.

This is an unnecessary tangent though, as I've said throughout this discussions, there's extreme cases and no doubt Google is likely one of them. But we're talking about common use case, to which I still haven't seen any evidences that GC pauses are a deliberating factor.

Re:Trying Rust for web services by portmanteaufu on Friday October 02, 2015 @02:02PM (#10320165)
You may already be familiar with this and are specifically concerned with GC. However, for what it's worth, it's not just the absence of garbage collection that makes languages like Rust and C faster. A huge piece of their performance is the level of control that they offer over types' layout in memory and where things get stored. Rust's preference for stack allocations and the absence of a mandatory per-Object size overhead (a la Java) really allow it to shine.
Re:Trying Rust for web services by jurre on Thursday October 01, 2015 @12:04PM (#10312141)
> PHP pages that take two or three full seconds to render

I don't use php personally, but most of my rails apps render full pages in under 100ms. I'd imagine php performance to be at least on-par with a full rails app.

Re:Trying Rust for web services by mtberatwork on Thursday October 01, 2015 @12:56PM (#10312601)
Once you start seeing hundreds or thousands of requests coming in per second and you see your cpu utilization sky rocket, then the "slowness" of the interpreted languages really comes into full play. Most apps/websites will never achieve this kind of load or scale though.
Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @01:35PM (#10312920)
> interpreted languages really comes into full play.

There are plenty of non-interpreted languages that don't require GC though. When you pick Rust you are picking manual memory management. Does even Google opt for non-GCed languages for their web servers?

Re:Trying Rust for web services by steveklabnik on Thursday October 01, 2015 @01:41PM (#10312969)
We've been having a debate lately, within Rust, if "manual" is really the right term here.

  {
      let x = Box::new(5); // malloc

  } // free
Is this really _manual_? In a sense it is, but it's very different than what most people think about. "Automatic" is kind of a good word, but Objective-C/Swift's "ARC" already covers that, and we don't do refcounting, so that could be misleading too.

Maybe "deterministic"?

Re:Trying Rust for web services by gmfawcett on Thursday October 01, 2015 @02:26PM (#10313414)
"RAII" seems to cover it nicely, and extends beyond memory management to other resources. Admittedly it's not a very friendly term for non-C++ programmers.

What's this non-lexical borrowing idea you mentioned in your other comment? (I can't reply there for some reason.) Is there an RFC for that?

Re:Trying Rust for web services by steveklabnik on Thursday October 01, 2015 @02:40PM (#10313546)
The relevant search terms are "SEME regions" and "non-lexical borrows". The tracking issue is here: https://github.com/rust-lang/rfcs/issues/811 and https://github.com/rust-lang/rust/issues/6393 is the older issue it superseded, with examples.

There hasn't been an RFC yet, because we're in the middle of a large amount of compiler internals work (HIR/MIR), which will make overall analysis easier, including these two features.

> (I can't reply there for some reason.)

HN limits responses based on the depth of the comment tree and the length of time since the comment was posted, to discourage flamewars, you can always click on a comment link directly to kind of bypass that though.

Re:Trying Rust for web services by gmfawcett on Thursday October 01, 2015 @03:17PM (#10313871)
Thanks for the issue link (and for the comment-tree depth hint!).
Re:Trying Rust for web services by acconsta on Thursday October 01, 2015 @03:29PM (#10314000)
Scope-bound resource management (SBRM) is clearer than RAII, I think.
Re:Trying Rust for web services by kibwen on Thursday October 01, 2015 @01:51PM (#10313042)
Memory management in C is also "deterministic", just forget to ever free. :P
Re:Trying Rust for web services by DasIch on Thursday October 01, 2015 @02:02PM (#10313161)
How about lexical memory management as a nod to dynamic vs. lexical scoping?
Re:Trying Rust for web services by steveklabnik on Thursday October 01, 2015 @02:09PM (#10313235)
That might work for now, but something we're working on for the future is making borrows non-lexical, so....
Re:Trying Rust for web services by kibwen on Thursday October 01, 2015 @02:34PM (#10313485)
Borrows may be non-lexical in the future, but deallocation via ownership will always be at the end of a lexical scope. Not only would eager deallocation be bad for performance, it's also a backcompat hazard at this point.
Re:Trying Rust for web services by yazaddaruvala on Thursday October 01, 2015 @02:32PM (#10313472)
I personally like:

Rust: "statically memory managed" Java, Go: "dynamically memory managed"

Similar to: "statically typed" or "dynamically typed"

Re:Trying Rust for web services by Tuna-Fish on Thursday October 01, 2015 @03:07PM (#10313771)
Statically memory managed already has a meaning. It means that there is no malloc during runtime, all memory addresses are decided (usually manually) beforehand and written into the executable.
Re:Trying Rust for web services by wyldfire on Thursday October 01, 2015 @02:36PM (#10313504)
I wouldn't call it manual at all. It looks remarkably like automatic storage duration IMO.
Re:Trying Rust for web services by phaylon on Thursday October 01, 2015 @07:04PM (#10315433)
Google suggests "affine memory management" is not yet used as a term.
Re:Trying Rust for web services by jerf on Thursday October 01, 2015 @12:12PM (#10312196)
I'm thinking Wordpress, or bespoke status pages for internal apps. Of course you can get a PHP page out in under a millisecond if you try hard enough, but it's often not used in that sort of place. (And it often is, but that still doesn't mean it often isn't.)

Rails, for that matter, is known for being easy to produce multi-second pages too.

Slow languages are slow in practice, too.

Re:Trying Rust for web services by jerf on Friday October 02, 2015 @09:33AM (#10318371)
It actually amazes me that people find the statement that slow languages are actually slow offensive and worthy of downvoting. As I said, it is my experience that simply switching from slow to fast languages even on "IO dominated" workloads has real, visible effects.

If you haven't tried it, consider trying it before becoming offended at the idea that your tool may not be appropriate for all use cases. Yes, it can matter when your language is 50 times slower than another.

Re:Trying Rust for web services by jamwt on Thursday October 01, 2015 @02:48PM (#10313621)
I think that line of thinking ends up not applying to rust terribly much.

I know there's been several articles lately about broader applications of rust, and then "is it worth it?" type responses, concerns about "manual memory management", with the implication being there's some heavy tax on not using a GC.

I would certainly agree with the presence of this tax while writing C/C++. (Less with C++, RAII, and especially c++11, but still there.)

With rust, once you're up the learning curve (which, granted, can take a few months), your productivity is not substantially worse than GC'd languages. You pretty much master the borrow checker's semantics, and the best practices to structure things in ways that play nicely with its expectations. And lifetime-related errors don't occupy all that much of your development time.

Source: my team has been re-writing some components of Dropbox's multi-exabyte storage system in rust (from go) over the last 9 months.

Re:Trying Rust for web services by acconsta on Friday October 02, 2015 @01:33PM (#10319968)
That might make you the biggest company using Rust? Very cool, I hope you write it up.
Re:Trying Rust for web services by pjungwir on Thursday October 01, 2015 @03:07PM (#10313774)
I am fascinated that no one uses Objective C on the back end. Fast, low memory, quick to code in, high-level-enough, a mix of static and dynamic typing, and no garbage collection. Also plenty of expertise you can hire for, maybe already within your company. I think if Obj C had a good story for deploying on Linux (and not losing modern features like ARC), it would make sense to use it, so we'd see sites doing it and open source tools like a good webapp framework. It is because you would need to run OS X servers? (And is that even true?)
Re:Trying Rust for web services by the-kenny on Friday October 02, 2015 @05:02PM (#10321309)
I think being so heavily pushed by Apple is actually a downside for ObjC here. I really enjoyed programming ObjC when I was programming for iOS and Mac. That was mostly because of the very rich API shipped with Apple products.

Can you point me to a list of libraries written in ObjC that work without Apple specific code? (E.g. without using anything starting with 'NS')

Re:Trying Rust for web services by mpvl on Sunday October 04, 2015 @04:19AM (#10326888)
Gnustep
Re:Trying Rust for web services by pjungwir on Monday October 05, 2015 @10:28AM (#10332009)
I'm aware of Gnustep, so I was hoping someone would mention it. But I was hoping for more than one word. How many people are using it in production? Have they had good experiences or bad? What are the surprises they've encountered? Does it have ARC support? Can I use XCode to build with it?
Re:Trying Rust for web services by dkhenry on Thursday October 01, 2015 @11:43AM (#10311932)
Two big benefits are the static typing and compilation so a I get a lot of benefit from catching errors early, and the second big benefit is static linking.

Other languages give you that ( namely Go ), but I found the correctness checking from rust is _way_ better and I am forced to have much better designs in my programs.

Another Tangential benefit is that I can do lots of great system level things ( High performance data collection, Clustering, Math), and then have a thread pull in a web server and serve out things like statistics and control interfaces.

Also its just nice to program in and the tooling is much nicer then C++

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @01:38PM (#10312942)
Thanks for your replying. Static typing I won't argue with you, but is static linking important for a web server?

One of the big areas where people choose Go is for cli utilities and static linking is a big reason for that choice. I can see Rust becoming a competitor in this space for the same reason. But for a web server that you control I don't see a huge advantage to static linking.

Re:Trying Rust for web services by dkhenry on Thursday October 01, 2015 @03:45PM (#10314110)
If I was just working in a SaaS world then maybe static linking isn't a big deal, but I ship and support software across 4 different versions of glibc, libstdc++, and any runtimes for various languages ( Java, python, php, ...). Also I have various versions of MySQL and command line tools. The only things I can guarantee I have are ssh and something that will respond to MySQL connections. In that world being able to push out a single binary and have it just work is priceless.
Re:Trying Rust for web services by neoCrimeLabs on Thursday October 01, 2015 @02:10PM (#10313244)
The one benefit of static linking is reduction of software/library dependencies required for production deployment. In many organizations this means you can develop on any OS/Platform you wish, and then deploy on whatever OS/Platform the ops team is currently running.

Many organizations have yet to adopt devops and templated system deployment methodologies, so it's a legit concern.

Re:Trying Rust for web services by Touche on Thursday October 01, 2015 @02:45PM (#10313593)
> In many organizations this means you can develop on any OS/Platform you wish, and then deploy on whatever OS/Platform the ops team is currently running.

That's true of dynamic linking as well. Static linking just saves you the trouble of having to install the library dependencies on the server. But for ops that's a pretty tiny, if not non-existent gain. So I don't buy it.

When deploying to users it's a huge gain, so I do get that that for things like cli utils.

Re:Trying Rust for web services by Scarbutt on Thursday October 01, 2015 @01:15PM (#10312749)
Depends on your definition of web server, nginx is written in C, even Ruby and Python web servers call to C, they need the performance of C implementations, so I don't see why Rust wouldn't be a good fit for a web server.
Re:Trying Rust for web services by shmerl on Thursday October 01, 2015 @11:53AM (#10312034)
Who said Web server doesn't fall into that category? It benefits greatly from better performance.
Re:Trying Rust for web services by Keats on Thursday October 01, 2015 @11:17AM (#10311719)
Ah that's interesting! Can you talk a bit more about the kind of project you're doing ?
Re:Trying Rust for web services by dkhenry on Thursday October 01, 2015 @11:35AM (#10311857)
My current project is an interface to get detailed application performance statistics off a clustered system. So it connects to a local database and has a configurable list of system checks that it can run. Then it has a defined API that is consumed by the Polymer front end. Rust is nice in that I can do all sorts of great clustering and network programming, and then have a thread that exposes the WebUI and all of that is wrapped up in a single binary. That I can just push to systems and execute.
Re:Trying Rust for web services by Keats on Thursday October 01, 2015 @01:17PM (#10312764)
It would definitely be interesting if you have time to push a sample project somewhere to see how it looks when it's someone that knows what they are doing.
Re:Trying Rust for web services by the_mitsuhiko on Thursday October 01, 2015 @02:04PM (#10313174)
I have some ideas for making hot reload work for web dev i just did not have the time yet :(
Re:Trying Rust for web services by vkjv on Thursday October 01, 2015 @10:54AM (#10311537)
What are the compile times like? Is a simple watch script with a re-compile sufficient?
Re:Trying Rust for web services by steveklabnik on Thursday October 01, 2015 @12:18PM (#10312245)
Not the parent, but they've gotten faster every release, so if you've tried Rust in the past, your previous experience would be wrong.

We're in the middle of a big refactoring of the compiler that will eventually enable even more gains. I'm confident rustc will only get faster in the future.

Re:Trying Rust for web services by kibwen on Thursday October 01, 2015 @12:28PM (#10312358)
You can't go evangelizing about compile times without even mentioning incremental recompilation. :P

https://github.com/rust-lang/rfcs/pull/1298