The possibility to test the compiler on almost all public Rust code is amazing, and it’s possible thanks to Cargo being the standard build system.
Can you imagine the effort to build and run tests on 30000 random C projects?
Perl has been doing this for over more than a decade, building and testing everything on CPAN. http://stats.cpantesters.org/
I gave a talk recently about how Perl’s monthly releases happen which covered this and more.
That’s amazing, I had no idea.
I actually was imagining that recently for benchmarking verification and testing tools. I found that they’re hosted in many places, use a bunch of different build systems, preprocessor magic that hurts reproducibility, and (see Coverity paper) most seem to pick a different dialect of C which may or may not be analyzable.
Just getting them all pulled and buildable for first benchmark would be a nightmare.
There are a lot of languages I think could theoretically do this. D for example could do with dub I would think.
Sure, all you need is a registry. But we’re doing it since… Forever.
Julia does something similar, I think
Busily finishing organising this year’s London Perl Workshop on Saturday including finalising the schedule this morning.
It looks like 10% of Internet users don’t use browsers that support this so I suggest it’s too early to declare CSRF dead.
This one is just one of many security features these browsers don’t have. If these users haven’t updated their browsers for so many years, they’re probably not installing regular security patches too.