There is plenty of spin, and 'patent dance' sounding talk, but the core idea seems to be 'multi threading' or time slice/serialize of the logic. That can save routing and LUTs but not save config memory and it will ADD the config-mux logic cost, between slice storage, and power impact.
The real test will come down to the SW, and if it will do the 'slice and dice' needed on the code, and if that will be debug-able.
10 years ago there were reconfigurable FPGA's. Is there something fundamentally diffferent about these?
I also question the phrase (spin?)
"We don't ask customers to do anything fundamentally different than they've done before,"
Please define "Fundamentally Different". Just coding for configurabnility is fundamentally different.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.