(Note I have no doubt you are right. It would just be a useful metric.)
(Note I have no doubt you are right. It would just be a useful metric.)
We've split the code up in crates so servo/servo is only a fraction of the story. Things in servo/servo are usually components which don't make much sense as something you'd independently use, and are very servo-specific and/or tightly coupled. But a lot of our Rust code is outside the tree, and any C++ modules we use are too.
Also, he vast majority of code in servo/servo is actually HTML/JS test code, vendored in tree from w3c/web-platform-tests.
Probably Github uses cloc. I downloaded the code (over 500MB, insane!) and cloc throws an error.
> and cloc throws an error
tokei is a similar program that's parallel, and written in Rust. It takes 11 seconds to run on my machine, and showshttps://gist.github.com/steveklabnik/b4ede6f13c9d609edc61d74...
(using a gist since the output is huge, and see Manish's comment as well)
Though not all that rust code is written specifically for servo, and a lot of that C/++ code is winapi and skia. winapi is autogenerated, and skia isn't used by default anymore iirc.