Sergio, I think Mike has a point (and the thread you linked to doesn't offer much in terms of justification as to why Yocto was chosen for the Edison). The situation appears to be better on the Edison (if I understand correctly, the Galileo didn't even have gcc on board).
It may be just me, but I suspect the reason behind using Yocto was somehow political. Intel may be (passively) trying to not cannibalize its tablet/laptop market by allowing the cheap Edison to be used for anything close to general computing. However, I have used Yocto before (some of the Olimex boards used to require it) and it's a bad bad bad choice for such a general purpose board. The Edison is also powerful enough (especially when you're coming from Arduino) to be able to run a lot of extra processes and tasks. This is not an Arduino Yun people, it has 1 GB of RAM, a dual core Atom and 4 GB of Flash, I think it's safe to say that most people coming from Arduino will not ever need all that processing power. Ok, some might, but those can get Yocto running or optimize Debian for their use (the minimal Debian install is just 200MB and leaves you with 1.2GB free space on /home/).
But the default should definitely _not_ be Yocto! You're driving people away, you're marketing this to makers, not hardcore embedded developers. Makers will not install the entire Yocto toolkit, figure out which packages they need, create their own image and flash it just to get an app running. They want to apt-get this and apt-get that and run - the Edison has plenty of power to allow this "sub-optimal" approach and that's why people want it. Otherwise they'll just go get an Arduino Yun in a ready-to-use package and forget about the Edison. And it's a pity, it's a great little board, you just need to get a community behind it. And that community wants the power of the Edison without the trouble of Yocto.
