4 ms·
Because unlike google code, this isn't going to be a hard dependency. When google code went down, existing sites (which used it as a CDN) broke and communities
by dispose13432 10y ago
Because unlike google code, this isn't going to be a hard dependency.
When google code went down, existing sites (which used it as a CDN) broke and communities broke up.
Here, you can do this on your own computer if you want.
It's like complaining that SF took down Compile Farm (which is actually worse, they had proprietary Unixen on their system).
- dgacmu 10y agoDefinitely this. The hard work, from my experience, in hooking up to a fuzzer is writing the wrappers to hook in to the fuzzer, and creating a set of examples from which to begin fuzzing intelligently. Automated fuzzing is the icing on top of that hard work. It magnifies the utility of doing the work to fuzz by making it run continuously and by throwing more computational resources at it to find more bugs. But, unlike, say, coding to some closed API where you're up a creek if the service goes away, most of the hard work is portable, and you can still run it on your own cluster. AFL and libFuzzer are open source and quite awesome on their own.
- hodgesrm 10y agoOK, thanks for the answers. We had product code on code.google.com and it was definitely a bummer when the site shut down. I'm possibly alone in the galaxy in saying this but I really liked their bug tracker which was lightweight but just functional enough to be really useful.