←back to thread

403 points jaytaph | 4 comments | | HN request time: 0.001s | source

Last year I wrote a post about trying to make a change in the world by writing a browser.

Today, we're excited to introduce Gosub, a new open-source browser engine that we are building from the ground up in Rust!

Gosub aims to be a modern, modular, and highly flexible browser engine. While still in the early development and experimentation phase, Gosub is shaping up nicely, and we’re looking to onboard more contributors to help us bring this project to life.

Some of the key highlights:

  * Written in Rust: We're leveraging Rust's safety and performance features to create a robust and efficient engine.
  * Modular Design: The project is organized around modules, allowing for clean separation of concerns and easier collaboration. It also allows us to easily swap components based on needs and allows more freedom for engine implementers in the future.
  * Collaborative and open source: We’re building Gosub with the intention of making it approachable and open to contributions, aiming to create a project that's easier to understand and collaborate on compared to existing browsers.
Instead of writing another shell around Chromium or WebKit, we decided to write a browser engine from scratch. We believe that having a diverse landscape of engines is the only way to defeat a monoculture that is currently threatening current browsers and by extension the internet itself. We cannot and should not let a very small number of large companies dictate the future of the web and its usage.

With Gosub, we're aiming to build something more approachable that can evolve with the latest web technologies, all while being open to contributors from day one.

We’re looking for developers with or without experience in Rust. You just need to be interested in browser technologies. There are plenty of opportunities to work on core modules, document our progress, and help shape the project's direction.

We can already render simple pages, including the hackernews front page. However, to render most sites correctly, it is still a long journey, so come and join us!

Show context
dustedcodes ◴[] No.41841205[source]
Why does it matter if it’s written in Rust?
replies(5): >>41841290 #>>41841350 #>>41841387 #>>41841734 #>>41843244 #
IshKebab ◴[] No.41841387[source]
Projects written in Rust tend to be very fast - as fast as C++ or C code - but without the endless security issues.

You may as well ask "why does it matter if this bridge is made of iron".

replies(1): >>41843523 #
PaulDavisThe1st ◴[] No.41843523[source]
There are long lasting bridges made of stone, concrete and in the right climates, even wood. Not to mention rope when it suits the purpose.

Each material has its own qualities, which means its own pros and cons in a given context.

This naive belief that there will be one language to rule them all (and is name is <fill-in-the-blank> ignores history and the world outside of programming in a rather silly way.

replies(3): >>41845193 #>>41845569 #>>41847715 #
1. IshKebab ◴[] No.41845569[source]
Nobody is saying that. But to continue your analogy, do you not think that in a world where all the bridges are made of wood it would be notable to say that a new bridge is made of steel?

Of course there are impressive projects made with C. But we generally don't build large bridges out of wood anymore do we.

replies(1): >>41850120 #
2. PaulDavisThe1st ◴[] No.41850120[source]
> do you not think that in a world where all the bridges are made of wood it would be notable to say that a new bridge is made of steel?

Notable, sure. But it could turn out to be Tacoma Narrows bridge.

We never did build large bridges out of wood, I think. For the right context, wood is still a preferred material for some bridges.

replies(1): >>41852782 #
3. IshKebab ◴[] No.41852782[source]
> We never did build large bridges out of wood, I think.

Yes we did. They just haven't survived. For example London Bridge was "various wooden bridges, AD 50 – 1176".

replies(1): >>41854547 #
4. PaulDavisThe1st ◴[] No.41854547{3}[source]
I guess "large" has a bit of wiggle room built in.