the idea: fritzing have to live on. that’s the main goal.
as it is for now there is no much more development and a list of more than 1000 bugs where nobody knows where to start … i could continue with many more examples.
for now i think the best way would be to keep things in free and open services. so we can handle the parts via github, as well as the maintaining for all of them. i love the idea to create a open and free hardware-based-library as well …
to come to your point: fritzing should become a web-service (imagine the power of a server in doing things like a complex copper fill …) but i want to say: it must stay an offline software, too.
from the performance perspective: a slim and well build, state of the art, webbased-software (hopefully without any bugs 
) and the ability to easily build extensions/plugins for it, would be faster than what we have now. and it would fit the needs of different users and their way how they wanna use fritzing.