We talk a lot in this blog about programming frameworks and how they help developers do their jobs in various languages. It seems at times that for any given programming language there is an endless list of frameworks available. This is great for us, because it gives us an endless stream of material for the blog.
There’s been a good deal of talk, in this blog and elsewhere, about the brave new world of the internet of things (IoT) and how it will transform our personal and business lives. The talk has been accompanied by no small amount of hype, with pundits proclaiming that there will be anywhere from hundreds of millions to trillions(!) of devices connected to the internet in the near future.
Images in apps and web pages are a bit like electricity, or the internet itself: You don’t notice them until they aren’t there. And when they aren’t there, the experience can be unpleasant.
When an image loads slowly or not at all, it’s easy to blame the network connection or the size of the image. However, there’s actually much more to it than that. An app’s ability to load images quickly depends in large part on the efficiency of its image processing routines, which use complex algorithms to load images as fast as possible without degrading image quality.
In the world of software development, enhancements in development tools and platforms tends to be incremental. Certainly, new tools, frameworks, and platforms that ease the job of software development or software project management come along with sometimes mind-spinning regularity, and we have discussed a good number of them in this space. But after that initial release, revolutionary enhancements of those tools in functionality, capability, and ease of use are pretty rare.
In enterprise computing, somewhere between the era of punched-card computers and the rise of the personal computer, there was the heyday of the mainframe and the “dumb terminal”—a keyboard and a monochrome monitor with no graphics capability, no mouse, no speakers, no webcam, no USB anything. One mainframe computer could support a large number of simultaneous users who logged in via these dumb terminals; they neither knew nor cared where the actual computer was located.
A friend recently shared an item on Facebook that described the top 10 developer excuses, including things like “it worked yesterday” and “you must have a virus.” The number one excuse: “It works fine on my machine!”