As someone who's always worked alone, I also find your opinion adorable, and will code socially when someone manages to hack their way into my ultra secure coding vault. Which I admittedly let people into for pairing. Sometimes.
Collaborative doesn't necessarily mean synchronous. We learned this building the real time building system in second life. Sometimes you just want to sit in your corner and know no one else is gonna come in, and not having that ability cuts off a huge portion of people who just don't work well in that circumstance. It's awesome to work offline, alone.
> Most of programming will be done socially [...] via
> small changes [...] from hundreds of people
This seems a little extreme. I'd venture that right now 'most of programming' is private code, or small side projects/toy code (i.e. single-developer projects).Of course, I'd never leave Emacs for Github when creating software from scratch or doing anything big.
What a nightmare.
I prefer very small teams whose members each have particular responsibilities so they're not stepping on each other, testing code before pushing out to the public.
A couple of decades, maybe.
Even then I disagree, but it's at least plausible.
Years though? I think you're over estimating how quickly this could possible happen.
In my opinion: In a couple of years we will not use Emacs or Visual Studio or anything like that: Most of programming will be done socially in Github via small changes directly from the website, from hundreds of people... it'd simplify the process of collaborative programming a lot.