feedback

Author: steveklabnik

_posts/2018-02-15-Rust-1.24.md

@@ -29,47 +29,45 @@ This release contains two very exciting new features: `rustfmt` and incremental
 
 For years now, we've wanted a tool that automatically can reformat your Rust code to some sort
 of "standard style." With this release, we're happy to announce that a *preview* of `rustfmt`
-can be used with 1.24 stable. Before we get into the details, here's how to install `rustfmt`:
+can be used with 1.24 stable. To give it a try, do this:
 
 ```bash
 $ rustup component add rustfmt-preview
 ```
 
-Notably, you should *not* install `rustfmt` through `cargo install`. Why not? Well, `rustfmt`
-relies on using the compiler as a library to do its job. As such, the exact right version of
-`rustfmt` for the exact compiler version you're using is critical, otherwise, it will not work.
-`rustup` knows what compiler version you're using, and so is able to pair it with the correct
-`rustfmt` version. Once you've added this component to a given toolchain, `rustup` will
-automatically update it as well. Run the command once, and then on every future
-`rustup update stable`, `rustfmt-preview` will be updated as well.
+There are two important aspects here: first, you're using `rustup component
+add` instead of `cargo install` here. If you've previously used `rustfmt` via
+`cargo install`, you should uninstall it first. Second, this is a preview, as
+it says in the name. `rustfmt` is not at 1.0 yet, and some stuff is being
+tweaked, and bugs are being fixed. Once `rustfmt` hits 1.0, we'll be
+releasing a `rustfmt` component and deprecating `rustfmt-preview`.
 
-> This strategy is expected to be used for other developer tools that integrate tightly with
-> the compiler, like the RLS and Clippy, in the future.
-
-Finally, please take note of that `-preview` in the name: `rustfmt` is still not quite
-at 1.0 yet. Some tweaks to the default styles are still occuring, though they're relatively
-minor. Once `rustfmt` hits 1.0, we'll be releasing a `rustfmt` component and
-deprecating `rustfmt-preview`. Since this is the first major component we're distributing
-this way, we wanted to clearly signal that it is still developing.
+In the near future, we plan on writing a post about this release strategy, as it's big
+enough for its own post, and is broader than just this release.
 
 For more, please check out [`rustfmt` on GitHub](https://github.com/rust-lang-nursery/rustfmt).
 
 #### Incremental compilation
 
-Back in September, we blogged about [Incremental Compilation](https://blog.rust-lang.org/2016/09/08/incremental.html).
+Back in September of 2016 (!!!), we blogged about [Incremental Compilation](https://blog.rust-lang.org/2016/09/08/incremental.html).
 While that post goes into the details, the idea is basically this: when you're working on
 a project, you often compile it, then change something small, then compile again. Historically,
 the compiler has compiled your *entire* project, no matter how little you've changed the code.
 The idea with incremental compilation is that you only need to compile the code you've actually
 changed, which means that that second build is faster.
 
 As of Rust 1.24, this is now [turned on by default](https://github.com/rust-lang/cargo/pull/4817).
-This means that your builds should get faster!
+This means that your builds should get faster! Don't forget about `cargo check` when trying
+to get the lowest possible build times.
 
 This is still not the end story for compiler performance generally, nor incremental compilation
 specifically. We have a lot more work planned in the future. For example, another change
 related to performance hit stable this release:
 [`codegen-units` is now set to 16 by default](https://github.com/rust-lang/rust/pull/46910).
+One small note about this change: it makes builds faster, but makes the final binary a bit
+slower. For maximum speed, setting `codegen-units` to `1` in your `Cargot.toml` is needed
+to eake out every last drop of performance.
+
 More to come!
 
 #### Other good stuff
@@ -95,7 +93,7 @@ See the [detailed release notes][notes] for more.
 
 ### Library stabilizations
 
-If you're a fan of `str::find`, used to find a given `char` inside of a `&str`, you'll be
+If you're a fan of `str::find`, which is used to find a given `char` inside of a `&str`, you'll be
 happy to see this pull request: [it's now 10x faster](https://github.com/rust-lang/rust/pull/46735)!
 This is thanks to `memchr`. `[u8]::contains` [uses it too](https://github.com/rust-lang/rust/pull/46713),
 though it doesn't get such an extreme speedup.