project VS Servo

It is now maintained by this club, I think: https://openwebdocs.org

Open Web Docs is a potential model to draw inspiration from regarding funding: https://openwebdocs.org

Presumably, PostgreSQL has leaders who are responsible for steering the ship. If the project is going to succeed long-term, those leaders have to find ways to keep their contributors happy while also creating an organizational structure that leads to good docs.

Sorry if any of my comments came off naive or obtuse when it comes to open source dynamics. But the reality is that you need good docs, and I'm just trying to give an honest assessment from my experience of the conditions that lead to good docs.

Estelle and the other folks working on Open Web Docs are on the receiving end of sponsorship, and she says she personally has a hard time asking for money. Or to reimburse things like a Grammarly subscription. "Will people get upset if the team meets up in person and uses sponsorship to cover air fare (which, to be clear, OWD didn't do)?"

> Elsewhere in this thread is a link to a separate organization called "OpenWebDocs," which appears to be an outside consortium that contributes to MDN.

Yes, that's what Open Web Docs is. It's funded by individual and corporate contributions, through https://opencollective.com/open-web-docs/. The money goes to pay writers (currently 2 full time, but we are hiring 2 more) to create and maintain independent open web documentation ("open" in the sense of accessible to everyone, "independent" in the sense that it shouldn't represent any one company's view). Currently our work is pretty much entirely focused on MDN, although that's not necessarily going to be the only thing we ever work on. Our 2021 high-level goals: https://github.com/openwebdocs/project/blob/main/2021-goals.... .

Open Web Docs long term roadmap will be published soon. However, the initial goals are focused on supporting MDN's recent infrastructure transition and contributing to core web technology documentation, browser compatibility data, and JavaScript documentation on MDN Web Docs.

Actually Servo development has accelerated greatly since 2023: https://github.com/servo/servo/graphs/contributors

https://servo.org/ is seeing new development alongside https://tauri.app/ which seems like it could replace Electron, getting them a little closer to native speed and memory usage.

It'd be nice to see more and more of Servo integrated into Firefox. Web pages rendered at 120fps and fewer memory leaks in long-lived many-tabbed browser sessions would be lovely.

Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine

> Is there any easy to use/hack HTML layouting engine where I could experiment with custom CSS attributes and bridge that gap? Would anything from Servo be suitable?

Servo could be used for this. You'd want to add support for parsing the CSS properties themselves to the style crate in https://github.com/servo/stylo and then the layout implementation to the layout2020 crate in https://github.com/servo/servo. You do effectively get a whole browser though.

I'm currently working on building a lighter weight / hackable layout engine based on a combination of https://github.com/servo/stylo (for css parsing and selector resolution), https://github.com/DioxusLabs/taffy (for box-level layout) and https://github.com/pop-os/cosmic-text (for flow/inline layout). I expect to have something decent in around 6 months

Neither of these setups currently have any support for pagination though.

Great to see some competition still alive in browser engine development. See also Servo (previously part of Mozilla) https://servo.org/ - that and Ladybird are still very underdeveloped compared to every day browsers.

It's a huge shame that there are no nightly builds of ladybird to try out but I assume that's because they just don't want the bug reports (if everything doesn't work it's pointless getting random bugs filed).

I haven't messed with it yet but from looking into it, this should absolutely work.

https://github.com/servo/servo/wiki/Building-on-ARM-desktop-...

don't know, there was a downtime in 2021 and 22 but since 2023, contributions look back to where it was before .. https://github.com/servo/servo/graphs/contributors

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

1. Servo