For another anecdote, Galaxy Nexus also supported BT 4.0 BLE with its Broadcom chip, but Google decided it wont enable it for 4.3 release. When I've found that out, it pissed me off immensely, so I found a solution how to enable the support and posted it as a flashable .zip on xda [1]. Same was also for N7 2012 and N10. After flashing BLE worked just fine.
Google doesn't care for its old devices, nor did it cared when it shipped, Nexus line was always awesome hardware, but not fully utilized by software, which is sad from an engineers point.
[1] http://forum.xda-developers.com/galaxy-nexus/development/mod...
If a hardware vendor pulls support for your product, it's almost always better to end of life the device.
A better argument is that vendors of consumer hardware should require that their partners sign up for long term support agreements where warranted. Let's not pretend that, just because a software company is big, they can force one of the largest chip vendors in the world to bow to their demands.
[edit] Just saw this comment that make sense : https://news.ycombinator.com/item?id=8943924
Secondly, I purchased a Galaxy Nexus from Google in late April, 2012 with the understanding that it would receive updates for at least 2 years. That is why I was very disappointed when it was not eligible for an update that arrived less than 18 months after I purchased it.
It is truely sad that a perfectly good phone is essentially e-waste, and cannot be used due to this bug.
Google Glass uses a TI OMAP SoC from the same generation (4430). The brand-new Moto 360 uses a TI OMAP SoC from the preceding (!) generation (3630).
Google Glass runs KitKat, the Moto 360 even runs Android Wear 5.
Neither the Glass nor Moto 360 suffer from this problem since neither has a cellular radio.
Even shipping 4.4 with a 4.3 kernel would be far superior to having what is essentially a brick.
What I mean here is that Google's move here is far from being only a support matter.
In retrospect it was a poor assumption on Google's part to think that these manufacturers were actually going to support their customers. That is why they have spend the last 2+ years re-architecting the system to shove a bunch of functionality into things that Google can update or libraries that developers can incorporate into their apps. I imagine when they started out, they did not intend to have a huge amount of the system in a support library that is packaged inside every single app. I bet they also didn't intend to have the bulk of new features be in the Google Play Services package. Yet here we are, largely because the manufacturers are much like PC makers in that they put their own interests far ahead of the ecosystem interests.