
We are pleased to announce the [1.0 release][ann] of Tokio, an asynchronous
runtime for the Rust programming language. Tokio provides the needed building
blocks for writing reliable networking applications without compromising speed.
It comes with asynchronous APIs for TCP, UDP, timers, a [multi-threaded,
work-stealing scheduler][sched], and more.

[sched]: https://tokio.rs/blog/2019-10-scheduler
[ann]: https://github.com/tokio-rs/tokio/releases/tag/tokio-1.0.0

Over the years, we have been delighted watching our users build amazing things.
For example, [Discord] used Tokio to reduce tail latencies 5x. [Fly.io] found
that, with Tokio, they can effortlessly meet their performance requirements and
focus on delivering features to their customers. For [the Zcash Foundation], building on Tokio
enables them to design misuse-resistant APIs. For AWS, their [Lambda][lambda]
team used Tokio to implement more reliable and flexible services.

[Discord]: https://blog.discord.com/why-discord-is-switching-from-go-to-rust-a190bbca2b1f
[Fly.io]: https://fly.io
[the Zcash Foundation]: https://www.zfnd.org/blog/futures-batch-verification/
[lambda]: https://aws.amazon.com/lambda/

The [tutorial] is the best place to learn how to get started with Tokio.

[tutorial]: https://tokio.rs/tokio/tutorial

# A stability guarantee

We first [announced] Tokio over four years ago. Since then, it has evolved
significantly. The most notable change happened a year ago with the addition of
[async and await][async_await] to Rust. Today, Tokio is easier to use and more
powerful. This evolution has also caused some friction. It has required
libraries to track these changes, and could result in confusing error
messages when accidentally depending on multiple versions of Tokio.

[announced]: https://medium.com/@carllerche/announcing-tokio-df6bb4ddb34
[async_await]: https://tokio.rs/blog/2019-11-tokio-0-2

The Tokio 1.0 release ends this churn. As part of the release, we are committing
to providing a stable foundation for the ecosystem. We have no current plans for
Tokio 2.0 and we commit to holding back on a Tokio 2.0 release for at least 3
years. We plan to maintain the Tokio 1.0 branch for a minimum of 5 years.
Tokio will keep a rolling MSRV (minimum supported rust version) policy of 6
months. When increasing the MSRV, the new Rust version must have been released
at least six months ago.

This stability does not mean Tokio will stagnate. We still have a lot of
work to do.

# 2021

We expect to focus on a few areas this coming year: `Stream`, `io_uring`, tracing
integration, and the Tokio stack.

## `Stream`

Today, the [`tokio-stream`] crate provides asynchronous iteration utilities
based on the Stream trait. An [RFC] to move the [`Stream` trait][Stream] from
[`futures-core`] to the Rust standard library is pending approval.

Once the standard library provides the Stream trait, Tokio’s stream utilities
will move into the Tokio crate itself.

[`tokio-stream`]: https://docs.rs/tokio-stream
[RFC]: https://github.com/rust-lang/rfcs/pull/2996
[Stream]: https://docs.rs/futures-core/0.3/futures_core/stream/trait.Stream.html
[`futures-core`]: https://docs.rs/futures-core/

## `io_uring`

[`io_uring`] is a new Linux interface providing asynchronous operations for all
types of I/O, including disk, while reducing the required number of syscalls.
Currently, on Linux, Tokio uses the `epoll(7)` interface, which notoriously does not
work for disk access. To work around this, Tokio provides asynchronous
filesystem APIs by dispatching synchronous operations to a thread pool. While
this works, it is not optimal.

By leveraging `io_uring`, Tokio will be able to provide genuinely asynchronous
filesystem operations. Additionally, early benchmarks of `io_uring` are very
promising and we are hopeful that these performance improvements will carry over
to Tokio.

[`io_uring`]: https://kernel.dk/io_uring.pdf

## `tracing`

Defining a first-class story around operating Tokio applications will be a focus
for 2021. A big part of this story will be tooling around tracing and metrics.
The [`tracing`] crate already provides much of the needed infrastructure. It
implements a facade layer and data model for structured diagnostics, allowing
both libraries and applications to emit machine-readable data that can be
consumed in a variety of ways.

Over the coming year, we will build deeper integration between tracing and the
rest of the Tokio stack. This integration will help provide the needed
visibility into Tokio's internals to answer questions. Questions like how you
can tune the Tokio runtime to reduce tail latencies, know what tasks are
currently running, or which locks are the most contended.

Furthermore, we will continue to improve and grow the rest of the `tracing`
ecosystem. This includes work towards new releases of the core `tracing` and
`tracing-core` crates, adding richer instrumentation to the libraries in the
Tokio stack, and providing integrations with other diagnostics and observability
tools, such as [`tracing-opentelemetry`].

[`tracing`]: https://crates.io/crates/tracing
[`tracing-opentelemetry`]: https://crates.io/crates/tracing-opentelemetry

## The Tokio stack

Tokio provides a runtime and asynchronous APIs for standard primitives such as
sockets and timers, but networking applications will often use higher-level
protocols such as HTTP and gRPC. The Tokio stack includes Hyper for HTTP and
Tonic for gRPC to address these needs. Today, we [released Hyper 0.14][hyperel]
with Tokio 1.0 support. Tonic will be updated shortly.

[hyperel]: https://seanmonstar.com/post/638320652536922112/hyper-v014

With Tokio 1.0 out the door, we will also focus on [Tower], a set of reusable
components for building reliable clients and servers.

[Tower]: https://crates.io/crates/tower

# Thanks

Tokio would not be possible without our many contributors, especially [Alice
Ryhl][alice], who has been invaluable to the project. Thanks to the leaders of
the Tokio stack libraries: [Sean McArthur][sean] (Hyper), [Lucio Franco][lucio]
(Tonic), [Eliza Weisman][eliza] (Tracing), and [Thomas De Zeeuw][thomas] (Mio).
Also, Tokio would not have been possible without [Aaron Turon][aaron]'s and
[Alex Crichton][alex]'s early involvement.

Finally, a big thanks is due to the companies who have financially supported
Tokio: [Mozilla], [Dropbox], [Buoyant], and [AWS].

[alice]: https://github.com/darksonn
[sean]: https://github.com/seanmonstar/
[lucio]: https://github.com/luciofranco
[eliza]: https://github.com/hawkw
[thomas]: https://github.com/Thomasdezeeuw
[aaron]: https://github.com/aturon
[alex]: https://github.com/alexcrichton
[Mozilla]: https://mozilla.org/
[Dropbox]: https://dropbox.com
[Buoyant]: https://buoyant.io
[AWS]: https://aws.amazon.com/

<div style="text-align:right">&mdash;<a href="https://github.com/carllerche">Carl Lerche</a></div>


Minecraft accounts for everyone.

Sublime represents the peak of reliablity and quality with our world class accounts offered at unparalleled prices. The final destination for all your needs.

Built by the community, for the community.

Tested and used extensively by long time, experienced members of the Minecraft community. We serve anyone from top competitive speedrunners to casual Bedwars players. We have the highest 5 star reviews from hundreds of satisfied customers.

- accounts sold so far!

Server unbanned

Our accounts are verified to be playable on Hypixel, Mineplex, CubeCraft, 2b2t, Wynncraft, and any other server.

Affordable pricing

We obtain accounts straight from the source, allowing us to bring you the highest quality accounts for cheap prices.

Client compatible

Our accounts are 100% compatible and usable with all Minecraft clients. Don't waste your time with custom authenticator software.

Bonus rank

Every account you buy has a bonus chance of having a rank on Hypixel up to MVP++, at no extra cost to you.

Secure payment

Pay securely and anonymously via one cryptocurrency payment. No hidden fees. No subscription. No interest.

What sets us apart?

Many other so-called "alt shops" provide cheap Minecraft accounts, but these accounts are illegally obtained through hacking. Our accounts are not "hacked" or "stolen" in any way.