Nickle vs Rocket

By default nickel catches all errors with its default ErrorHandler and tries to take reasonable actions. In cases where one wants to provide an own ErrorHandler (e.g. for custom 404 pages), it's trivial to write one

Nickel supports defining templates with mustache.rs. All you need is to create the template

nickel makes it easy to map JSON data right onto your struct

Middleware are the extensibility points of nickel. Batteries included! A bunch of existing Middleware comes right with nickel

Routes can be as simple as /foo, use parameters, wildcards or even double wildcards

Rocket makes extensive use of Rust's code generation tools to provide a clean API.

Rocket streams all incoming and outgoing data, so size isn't a concern.

View, add, or remove cookies, with or without encryption, without hassle.

Unit test your applications with ease using the built-in testing library.

Easily create your own primitives that any Rocket application can use.

Rocket makes rendering templates a breeze with built-in templating support.

Handling query strings and parameters is type-safe and easy in Rocket.

From request to response Rocket ensures that your types mean something.

Spend your time writing code that really matters, and let Rocket generate the rest.

Configure your application your way for development, staging, and production.