diff --git a/server/templates/community.hbs b/server/templates/community.hbs index 5fb68f2d41754752c7a696821f5f0ed80cbc4760..8b3926613a25d5bbfb7059ca7f7c4eb5c773276b 100644 --- a/server/templates/community.hbs +++ b/server/templates/community.hbs @@ -2,9 +2,8 @@

We’re building a community of passionate developers & advocates.

-

We think there’s a better way to write code, and we hope to share it with you soon.

-

If you would like to get involved early, sign up for the Zed Universe community below and we will let you know when it opens.

+

If you would like to get involved early, sign up for the our community below and we will let you know when it opens.

- + - +
- - -

- We'll never spam you — You can expect an email every 1 to 3 months from us if you sign up for updates, and occasional emails about public testing releases. + We're not gonna spam you — You can expect an email every 1 to 3 months from us if you sign up for updates and occasional emails about beta releases.

diff --git a/server/templates/home.hbs b/server/templates/home.hbs index c025b311e01b009153cbddf70baa177cd7082914..442677c412e262ffbe84c3beaff5362298aabbe2 100644 --- a/server/templates/home.hbs +++ b/server/templates/home.hbs @@ -1,6 +1,6 @@ {{#> layout }} -
+

Introducing Zed—A lightning-fast, collaborative code editor written in Rust.

@@ -51,28 +51,49 @@

Under the hood

-

Rust

-

With performance and reliability being our priority, writing Zed in Rust was an obvious choice.

- -

In the past to write software with this performant you would need to use C++. Rust, for the first time, enables us to write software at that level as a very small team.

- -

GPUI

-

While Rust enables us to build performant, reliable software, it's constraints make rending custom UIs a challenge. To attack this, we created gpui, a rust library that rethinks the entire rendering stack that goes all the way to the graphics hardware.

+
+

Rust

+

Rust offers expressivity and developer productivity rivaling languages that depend on a VM, while simultaneously offering the control required to fully utilize the underlying hardware.

+ +

Rust’s unique ownership model is a challenge at the beginning, but once you internalize it, you can write extremely efficient multi-core code without fear of invoking undefined behavior.

-

We started gpui as an extension of that desire to write apps that are fast and fluid, yet easy to develop itteratively. gpui rethinks the way we draw UI in response to the constraints of Rust. By controlling the entire stack we remove layers of extra code that would reduce performance.

- -

Without building gpui the most viable way to build a cross-platform app would have been Electron. It's well documented performance limitations and single threaded nature made it a deal-breaker for us. Taking full advantage of local hardware was important to use to ensure that we can squeeze out the best performance.

- -

We’re building gpui and Zed in parallel, and may consider opening gpui up for usage outside of it in the future.

- -

CRDT

-

Like gpui enables performant UI, crdt is the key to making code collaborative as it is being written.

- -

A crdt allows us to version control the codebase on the keystroke level—Every keystroke can be revisited, commented on or undone. Entire sessions can be replayed and scrubbed in a session, from the point of view of any player.

+

It also makes it straightforward to call directly into the C-based APIs of the operating system. Rust makes it possible for a small team to build a complex product quickly, and Zed wouldn’t have been possible without it.

+ +

In the past to write software with this performant you would need to use C++. Rust, for the first time, enables us to write software at that level as a very small team.

+
+ +
+

GPUI

+

We originally planned to use Electron as a convenient means of delivering a cross-platform GUI for Zed while building the core of the application in Rust. But at every turn, we found that web technology was the bottleneck in achieving amazing performance.

+ +

Finally, we decided to take full control and simply build a GPU-powered UI framework that met our needs. We call it GPUI.

+ +

We took a lot of inspiration from Mozilla’s Webrender project. The key insight was that modern graphics hardware can render complex 3D graphics at high frame rates, so why not use it to render relatively simple 2D user interfaces with an immediate mode architecture?

+ +

Rust’s ownership model required us to rethink much of what we learned in other UI programming paradigms, but the result is a framework that’s productive to use and remarkably easy to reason about.

+ +

It’s liberating to control every pixel, and it’s a rush to push those pixels at lightning speed.

+
-

This level of granularity in our version control allows us to explore ideas like time traveling the codebase.

- -

Often the best way to understand code is to experience it's creation chronologically. Imagine if you could jump to the point a piece of code was created and watch it be written in real time.

+
+

Conflict-free replicated data types

+ +

Real-time collaborative editing presents the illusion that multiple people are editing the same buffer. In reality, each collaborator maintains their own personal replica of the buffer to which they can apply local edits immediately without network latency.

+ +

After being applied locally, edits are transmitted to collaborators over the network, whose copies may have also changed in the meantime. This means that as participants edit together, their replicas continuously diverge and reconverge. Turns out this is a tricky problem.

+ +

To solve it, we’re using conflict-free replicated data types, which have emerged in the last decade as a general framework for achieving eventual consistency in a variety of circumstances.

+ +

Making Zed’s buffers CRDTs allows for collaborative editing, but it also helps us reason about concurrent change so that we can push work into background threads and keep the UI thread responsive.

+
+ +
+

Tree-sitter

+ +

We plan to integrate with the Language Server Protocol to support advanced IDE features, but we also think it’s important for a code editor to have a rich, native understanding of syntax.

+ +

That’s why we built Tree-sitter, a fast, general, incremental parsing library that can provide Zed with syntax trees for over 50 languages. Tree-sitter already powers production functionality on GitHub, and we’ll use it to deliver syntactically-precise syntax highlighting, tree-based selection and cursor navigation, robust auto-indent support, symbolic navigation, and more.

+

———

diff --git a/server/templates/partials/layout.hbs b/server/templates/partials/layout.hbs index 94d05acdc9faa7b731c076d7de6fac1cfb8231ef..637e2ffd576c66e546a4484742d6baa7130550f3 100644 --- a/server/templates/partials/layout.hbs +++ b/server/templates/partials/layout.hbs @@ -34,13 +34,31 @@
-