Microsoft (and a lot of other PC developers ) should take note of this. So much of today's SW is bloatware, written as if memory and hard disk space are entirely free. They never consider that if a program exceeds the available cache space it will run ten times slower and if it has to be swapped to hard disc it will become almost unusable. This something that everyone seems to have lost sight of. Because of it we have 3GHz computers that run like they are only 100MHz computers. Sure there are some applications that use gigabytes of RAM, but 4GB for a word processor? give me a brake. A lot of it is because people use MS visual C++ which I once used to compile a small program that was 25k under MS C version 5.0 yet with whatever version was available in 2008 compiled to almost 300k. That codee has to be loaded from disk, share the cache (if it wants to run fast) reside in RAM along with all the others and share its execution time. If it gets all of it's work for one cycle done in one OS tick (a 26k program will do that) it will be snappy indeed, where as the 300k program (doing the same thing) will likely not and have to split its time over several ticks.
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.