This was one month after it's release
Nokia Lumia 610 can't install Angry Birds, Skype and more | CNET UK and months before WP8 came out.
In 2 years time a basic dual-core with 512mb will not be enough on a WP! By then a basic quad-core with 1GB ram will probally not be enough for Android
As a5cent said, this has to do with the software divide between WP7 and WP8.
Mirtas, thanks for citing a specific example.
You fear future apps may not run well on current WP8 hardware. You think getting a quad core WP8 device now will remedy that problem. That is wrong for many many many reasons, but again, I'll concentrate just on the one example you provided. You cited Angry Birds as a precedent for such a problem in WP's past, because Angry Birds didn't run on the L610 on the day it was released. This is why that argument doesn't work:
1)
WP8 and WP7 devices are each available in two different RAM configurations. Either as 1 GB or 512 MB models (WP8) or 512 MB and 256 MB models (WP7). Microsoft was always upfront and clear about the limitations of those devices with less RAM: they will run any normal app, but not necessarily every game. The L610, the device you cited, is precisely such a 256 MB model! It was never intended to run every possible game. Therefor, this example has no bearing on the argument you are trying to make:
Anyone who buys a 512 MB WP8 device today, and one year from now claims that the devices is outdated because it can't run every game, is severely bending the truth. Again, it was never intended to play every game, from the outset! The only honest statement is to say it was under spec'ed from the outset, at least for its intended purpose.
2)
In the case of Angry Birds, the CPU was never a problem. It was only ever about this RAM limitation. However, a later update solved the problem. Now, Angry Birds runs just fine on WP7 devices with 256 MB of RAM. In all honesty, what this really shows is that there NEVER was a hardware problem of any kind! This was just sloppy programming.
3)
The point is, you can't cite an example in WP's past where the issue you're raising was ever a problem. Although the past can't be used to predict the future, this should at least show you that WP, at least so far, isn't really comparable to Android in this regard.
I'm guessing you are taking experiences made in the Android world and applying them WP. That simply doesn't work. How Microsoft manages WP as a combined and standardized hardware/software platform is simply too different.