Funny that the same issue has an article on how M2M is giving way to IoT:
Now, IoT does split the whole thing into 'dumb pipe' and some value-added services, where telecom companies have to compete on even terms with everyone else---and telecom companies don't have the best track record in this area. As a random example, Verizon has an app, MyVerizon, that is supposed to be a service portal for their cellular customers. The app is atrocious and is universally panned by users.
In the article you referenced, the author distinguishes M2M from IoT largely on the basis of the types of networks they connect to -- cellular for M2M vs. something new for IoT.
In that sense, both articles seem to be saying much the same thing -- that the cellular networks are not optimal, either technically or economically, for the billions of "things" that will be communicating with each other, without human involvement, in the coming years.
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.