Servo VS System76 Power Management

> 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

To pain broad strokes, the layout phase (~= take the HTML, take the CSS, determine the position and size of boxes) is largely sequential in production browser engine today. Selector matching (~= what CSS applies to what element) is parallel in Firefox today, via the Stylo Rust crate originally developed in the research browser engine Servo. Servo can do parallel layout in some capacity (but doesn't implement everything), https://github.com/servo/servo/wiki/Servo-Layout-Engines-Rep... is an interesting and recent document on the matter.

Parallel layout is generally considered to be a complex engineering problem by domain experts.

https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en... is a really cool article that is related, that is a few years old but what it says is largely correct today.

[Article author/submitter here]

I can only tell you that it is not what this is about, inasmuch as I was at the talk and there was not a single mention of Firefox Reality or Wolvic in the talk.

Wolvic might use Servo – but I think if it did they would mention it, right?

The talk didn't and the word "Wolvic" does not occur anywhere on https://servo.org

So I am guessing not, no.

Igalia has -- or rather is because it's a co-op -- about 100 developers. They are not all working on the same thing.

If Rust is a must, surely contributing to Servo[1] and learning by sending small PRs to start with would be more beneficial.

However, I do understand as I've done this kind of "from scratch" project before just because I thought I could do it better or because I couldn't get into reading the existing codebase easily. To each their own...

[1] https://github.com/servo/servo

[Update 2022-02-21] It appears that there are two packages, System76-io-dkms and System76-power. From what I gather only the first is necessary. I'm not sure how to install third-party DKMS modules that are not in the official repos. The official Void documentation on this topic is sparse, is there somewhere I can look this up?

system76-power

The performance modes are going to affect how much power the system is using (and thus how much heat it's generating), not the fan curves directly. Those profiles are defined in the system76-power application, source code here: https://github.com/pop-os/system76-power/blob/master/src/daemon/profiles.rs

The script uses udev rules that are run at specific kernel events. It creates one rule for when the Laptop switches to battery power and another for when the Laptop switches to wall power. Both rules run system76-power while providing one of the available power profiles as an argument. I went with battery and balanced respectively.

I can confirm on my end that the fix here worked and I've mentioned it in the bug report.

thats provided by system76-power https://github.com/pop-os/system76-power you can heave it easily on arch (or everywhere else) it´s well documented by system76 https://support.system76.com/articles/system76-software/ as mentioned by the guys before, if you plan to run kde plasma you could also stay on arch or maybe fedora or something else :). pop-os has a very well designed gnome based desktop (cosmic) if you go for kde i suggest you will get an older version from ubuntu / debian repositorys.

Have any of you used tools like system76-power (PopOS power manager) or envycontrol on a Dell XPS? How well do they work?