-### Features:
-
-* syntax highlighting (LSP does not have API for it, so impl is hacky
- and sometimes fall-backs to the horrible built-in highlighting)
-
-* commands (`ctrl+shift+p` or keybindings)
- - **Show Rust Syntax Tree** (use it to verify that plugin works)
- - **Rust Extend Selection** (works with multiple cursors)
- - **Rust Matching Brace** (knows the difference between `<` and `<`)
- - **Rust Parent Module**
- - **Rust Join Lines** (deals with trailing commas)
+To try out the language server, see [these
+instructions](./editors/README.md). Please note that the server is not
+ready for general use yet. If you are looking for a Rust IDE that
+works, use [IntelliJ
+Rust](https://github.com/intellij-rust/intellij-rust) or
+[RLS](https://github.com/rust-lang-nursery/rls). That being said, the
+basic stuff works, and rust analyzer is developed in the rust analyzer
+powered editor.
+
+
+## Current Status and Plans
+
+Rust analyzer aims to fill the same niche as the official [Rust
+Language Server](https://github.com/rust-lang-nursery/rls), but uses a
+significantly different architecture. More details can be found [in
+this
+thread](https://internals.rust-lang.org/t/2019-strategy-for-rustc-and-the-rls/8361),
+but the core issue is that RLS works in the "wait until user stops
+typing, run the build process, save the results of the analysis" mode,
+which arguably is the wrong foundation for IDE.
+
+Rust Analyzer is a hobby project at the moment, there's exactly zero
+guarantees that it becomes production-ready one day.
+
+The near/mid term plan is to work independently of the main rustc
+compiler and implement at least simplistic versions of name
+resolution, macro expansion and type inference. The purpose is two
+fold:
+
+* to quickly bootstrap usable and useful language server: solution
+ that covers 80% of Rust code will be useful for IDEs, and will be
+ vastly simpler than 100% solution.