Servo VS xsv

> I mentioned momentum for a reason, servo doesn't have any. Ladybird however is extremely actively developed.

Looking at https://github.com/servo/servo it's very actively developed and gaining new contributors. The number of contributors for both projects is very similar. They are both active.

I felt like this link is missing some important context.

History: Initially started by Mozilla in 2012. They laid off the team off in 2020 and transferred the project to the Linux Foundation. Source: https://en.wikipedia.org/wiki/Servo_(software)

2025 Roadmap: https://github.com/servo/servo/wiki/Roadmap

At this point, I believe, it's important to accelerate development of Servo[1], which not only provides better browser security because of memory safety (getting rid of the stupid mistakes like OOB access or UAF), but is also managed[2] by Linux Foundation Europe[3], which gives more hope from the privacy standpoint.

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

[2] https://servo.org/about/

[3] https://linuxfoundation.eu/

I understand that people need alternatives that work now but please consider contributing your developer expertise and/or donating to Ladybird[0] / Servo[1]. We need to get away from our current engine monoculture of Chromium/Gecko (yes I know webkit exists)

[0]: https://ladybird.org

[1]: https://servo.org

Ladybird is lucky in that it has someone who knows how important marketing is, even for opensource projects. There are other opensource browser engine projects languishing because of lack of PR, patronage and / or volunteers. For e.g. NetSurf https://www.netsurf-browser.org/ - website is outdated because of lack of volunteers, but the project has active development - https://source.netsurf-browser.org/netsurf.git/ (already has partial support for CSS3, and Flex layout). Servo (https://servo.org/) is another but it gets some decent PR because of its Rust codebase and the Rust PR team.

It seems that they moved it since to a bigger meta issue and it's actively being worked on https://github.com/servo/servo/issues/30593.

https://github.com/servo/servo

Servo is upcoming, but so far it is fantastic in comparison to any other browser out there.

I tend to focus on any software that does not require 12 teams of people 6 weeks to determine how to build a single binary because of the use of 20 different programming languages and mixing and matching of paradigms and solutions to subconponents.

qsv is a command-line tool to work with CSV files. It is the successor of xsv and is written in Rust. Current progress is quite impressive as qsv now has SQL and Lua support.

Let's say, we want to write an extension that lists all the repositories of the user. The extension is a simple shell script that uses the gh command to list the repositories current user owns and tabulates with xsv command:

I cannot imagine any way it is worth anyone's time to follow this article's suggestion vs just using something like zsv (https://github.com/liquidaty/zsv, which I'm an author of) or xsv (https://github.com/BurntSushi/xsv/edit/master/README.md) and then spending that time saved on "real" work

I realize it's not really that comparable since these tools don't support SQL, but a more fully functioned CLI tool is - https://github.com/BurntSushi/xsv

They are both fairly good

I have done some similar, simpler data wrangling with xsv (https://github.com/BurntSushi/xsv) and jq. It could process my 800M rows in a couple of minutes (plus the time to read it out from the database =)

xsv, which seems to be why qsv was created.

[1] https://github.com/BurntSushi/xsv/issues/267

CSV utilities (still haven't pick a favorite one...): https://github.com/harelba/q https://github.com/BurntSushi/xsv https://github.com/wireservice/csvkit https://github.com/johnkerl/miller