diff --git a/crates/server/src/careers.rs b/crates/server/src/careers.rs new file mode 100644 index 0000000000..bedb35f745 --- /dev/null +++ b/crates/server/src/careers.rs @@ -0,0 +1,15 @@ +use crate::{AppState, Request, RequestExt}; +use std::sync::Arc; +use tide::http::mime; + +pub fn add_routes(app: &mut tide::Server>) { + app.at("/careers").get(get_careers); +} + +async fn get_careers(mut request: Request) -> tide::Result { + let data = request.layout_data().await?; + Ok(tide::Response::builder(200) + .body(request.state().render_template("careers.hbs", &data)?) + .content_type(mime::HTML) + .build()) +} diff --git a/crates/server/src/main.rs b/crates/server/src/main.rs index 0f4bddc216..4b5780af68 100644 --- a/crates/server/src/main.rs +++ b/crates/server/src/main.rs @@ -12,6 +12,7 @@ mod home; mod releases; mod rpc; mod team; +mod careers; use self::errors::TideResultExt as _; use ::rpc::Peer; @@ -178,6 +179,7 @@ pub async fn run_server( api::add_routes(&mut web); home::add_routes(&mut web); team::add_routes(&mut web); + careers::add_routes(&mut web); releases::add_routes(&mut web); community::add_routes(&mut web); admin::add_routes(&mut web); diff --git a/crates/server/templates/careers.hbs b/crates/server/templates/careers.hbs new file mode 100644 index 0000000000..4c6aaa6247 --- /dev/null +++ b/crates/server/templates/careers.hbs @@ -0,0 +1,20 @@ +{{#> layout }} + +
+

+ We think there's a better way to write code—and we've been working for more than a decade to bring it into existence. +

+

Zed is looking for a Rust engineer to help us advance the art of code editing. We're currently three engineers and a designer developing a new editor with a focus on performance, clean design, and collaboration.

+

We're working on exciting technologies, including a custom, GPU-accelerated UI framework, heavy use of parallelism and persistent data structures, conflict-free replicated data types, and an incremental parsing framework called Tree-sitter that was created by one of our founders.

+

Our codebase consists of about 60,000 lines of well-factored, thoroughly-tested Rust that compiles quickly. In addition to the Zed editor, we're also developing a server-side component to facilitate collaboration that tightly integrates with the client.

+

We'd love to hear from you if you're excited to build the world's best code editor and meet this description:

+ +
+ +{{/layout}} diff --git a/crates/server/templates/home.hbs b/crates/server/templates/home.hbs index da2fe8f976..4d476da35e 100644 --- a/crates/server/templates/home.hbs +++ b/crates/server/templates/home.hbs @@ -4,7 +4,7 @@

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

- We think there’s a better way to write code, and it starts with the following assumptions: + We think there's a better way to write code, and it starts with the following assumptions:

Mission-critical tools should be hyper-responsive.

@@ -20,11 +20,11 @@

Real-time collaboration produces better software.

- Pull requests have their place, but sometimes you just want to code together. It’s more fun than code review, builds trust between colleagues, and it’s one of the best ways to distribute knowledge through a team. But it has to be easy. + Pull requests have their place, but sometimes you just want to code together. It's more fun than code review, builds trust between colleagues, and it's one of the best ways to distribute knowledge through a team. But it has to be easy.

- If you want someone’s perspective on a piece of code, it should be as easy as sending a message to pull them into your working copy and start coding. + If you want someone's perspective on a piece of code, it should be as easy as sending a message to pull them into your working copy and start coding.

Conversations about software should happen close to the code.

@@ -40,7 +40,7 @@

Our goal is to make you as efficient as possible.

- If you’re living in a tool for hours every day, you want it to disappear. Every pixel must carry its weight, and the software you’re creating should always be the focus. So we constantly ask ourselves how we can maximize signal and minimize noise. + If you're living in a tool for hours every day, you want it to disappear. Every pixel must carry its weight, and the software you're creating should always be the focus. So we constantly ask ourselves how we can maximize signal and minimize noise.

@@ -49,15 +49,21 @@

———

+

+ We're looking to add another engineer to the team. Want to help us build the future? Join us. +

+ +

———

+

Under the hood

Building in 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.

+

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.

-

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.

+

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.

@@ -68,11 +74,11 @@

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?

+

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.

+

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.

+

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

@@ -82,17 +88,17 @@

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.

+

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.

+

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.

+

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.

+

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/crates/server/templates/partials/layout.hbs b/crates/server/templates/partials/layout.hbs index 3a39eeda3c..fe5d37d12a 100644 --- a/crates/server/templates/partials/layout.hbs +++ b/crates/server/templates/partials/layout.hbs @@ -114,6 +114,12 @@ The Team + + + Careers +