That's very negative, despite the disclaimer. And from what I've seen of the above, people aren't writing ten crappy side projects, many of them are excellent.
Staying focused on one thing is fine too, but for many of us, we like to dabble in many things.
If Giotto is your way of learning python and building another (python) web framework then that's fine too. One difference is that many of the above side projects are new and do things that we didn't have prior to someone building them, meanwhile yet another web framework a la bottle et al is really contributing very little new.
Its not about size, its about length of development. Great software takes more than a few days to create. I think the most direct indicator of software quality is number of commits. A project with 10 commits is probably full of bugs. A project with 400 commits has probably had enough chance to adapt really well to whatever problem it is supposed to be solving. Its not a direct correlation, but its usually true.
I've had co-workers who had 50 github repos all filled with 30 line "projects" with 5 commits each. Those types of projects don't make you a better programmer. Work on the same project all year. That will make you a better programmer. Craft the project. Let it adapt. Test it, deploy it. Tweak it. Deploy it again. Seek feedback from users. Tweak it some more. Going through that process will make you a better programmer.
Staying focused on one thing is fine too, but for many of us, we like to dabble in many things.
If Giotto is your way of learning python and building another (python) web framework then that's fine too. One difference is that many of the above side projects are new and do things that we didn't have prior to someone building them, meanwhile yet another web framework a la bottle et al is really contributing very little new.