←back to thread

403 points jaytaph | 2 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
chasil ◴[] No.41840824[source]
Would a fork of Chromium that was restricted to MISRA-C/C++ offer any real security advantages?

Would parts of Chromium be fundamentally incompatible with these standards?

https://en.wikipedia.org/wiki/MISRA_C

replies(3): >>41841142 #>>41841296 #>>41841343 #
1. ratmice ◴[] No.41841296[source]
I would think the MISRA rules against dynamic memory allocation would present serious difficulty if not fundamental incompatibility when trying to implement web standards.
replies(1): >>41841774 #
2. chasil ◴[] No.41841774[source]
It is against the rules to call malloc, yes.

However, it is not against the rules to launch another process with a static amount of declared memory, then access it over shmat().

This is cheating, but could it be safer?