While I love that idea in theory, it could present so many little issues that I can understanding holding out for a "big" update.
The problem with that is the updates still have to go through QA testing from verizon because they use Verizon's radios, so it's not like Google can directly push the update (as they should be able to) OTA like Microsoft pushes updates to PCs. QA through Verizon takes time, and ultimately we would still be waiting forever for updates.
Plus These are cell phones and because of that they NEED to be 100 percent certain they will work as intended when it comes to an emergency.
Isn't this another type of question that is asked each time a thread like this is started? As far as attempting to follow the Microsoft model. There is one huge difference that comes to mind on that one. Microsoft doesn't use a single phone companies network to transfer their updates. Where with these updates, the phone company's network is being used.
I also find some of these threads to include some of the unrealistic and often times unreasonable demands that are similar to what we saw while waiting for the phone to be released. There is a difference between rumors and an actual announcement made by Google regarding a release of an update. I doubt that a VZW employee is going to be privy to Googles development and release schedule, especially for an update like this.
Let's all look at history shall we.
Android 1.0 - Sept 23, 2008
Android 1.1 - Feb 9, 2009
Android 1.5 - April 30, 2009
Android 1.6 - Sept 15, 2009
Android 2.0 - Oct 26, 2009
Android 2.0.1 - Dec 3, 2009
Android 2.1 - Jan 12, 2010
Android 2.2 - May 20, 2010
Android 2.3 - Dec 6, 2010
Android 2.3.3 Feb 9, 2011
Android 2.3.4 Apr 28, 2011
Android 2.3.5 Jul 25, 2011
Android 2.3.6 Sept 2, 2011
Android 2.3.7 Oct 10, 2011
Android 3.0 Feb 22, 2011
Android 3.1 May 10, 2011
Android 3.2 Jul 15, 2011
Android 3.2.1 Sept 20, 2011
Android 3.2.2 Aug 30, 2011
Android 4 Oct 19, 2011
As much as i'd love to believe all these comments, historically I fail to see how 'difficult' it is for updates to roll through (and these were on non nexus phones). Perhaps yes, the updates can come faster than the service provider can send these through but a lot of the little updates were done in a regular timely manner.
I mean look at the time it took for the GNex to hit US shores from when ics was released.
Are you guys kidding me on these excuses about how difficult a new version is released?
Take for example
Android 2.3.6 Sept 2, 2011
It fixed a voicemail bug. There was a wifi bug and they fixed it later that month.
The following month they released
Android 2.3.7 Oct 10, 2011
To introduce Google wallet to the Nexus S ironically something we don't have. So they had a bug, released a fix, then found another bug and released another 2 weeks later fix, then they introduced wallet another few weeks later.
Read the whole friggin timeline, it's not a "theory" it's not "wishful thinking", they have the ability and Verizon is probably the culprit, but don't talk about timelines like because this is new it's extra slow is a valid excuse cause it's not. I'd be more willing to accept the it's more difficult excuse over that.
We all really don't know and will not know what's holding stuff up, but it is clear that their once fairly steady flow of releases and updates, not to mention the release flub isn't very people friendly.