Definitely, my major concern though is that AMD is sticking with the party line of anything over 2667 is overclocking and you're on your own. Now AMD can establish a reputation that Ryzen can easily hit say 3333, perhaps similar to how Haswell-E was able to reliably clock to ~4.5 GHz (BCLK to 1.25, 1.3 volts, multipler to 36 and after that the only question was how low you could get the voltage while being stable), and do really well in the enthusiast community do to the ease of the OC and Ryzen's cost per core. But it still hurts them in the workstation space. We'll OC certain times of developer machines and such because they don't do critical stuff (for example our CI server will run their tests again and validate all work done on the dev box), but others we won't touch since the work product they produce goes directly to clients, they need to certain tasks whose completion times are measured by hours so even slight instability and rare crashes creates a problem due to the rerun time, etc. Ryzen kind of firmly takes itself out of the game there, since cross CCX communication on 2667 is pretty painful. Most businesses are going to buy Intel there because even if the user only does stuff that would trigger cross CCX communication 5% of the time, the Intel price premium is totally offset by what your employee costs per hour.

Hopefully for Ryzen 2 or whatever they call the next one, they can officially support 3000 or better right out of the box. Even if it is just on the more premium chipsets. Right now workstations are really where the higher core count Ryzens can gain traction.