The short answer is that it isn't. IT still does the same things it once did. What changed for me is the feeling of intent. Enable GPS has the appearance of being a device-oriented command; Users feel that they are toggling a little subdevice on or off. The thinking is "I want my phone to know where it is. I'll turn on the GPS". Location Service has a somewhat different emphasis. In this case, focus is on the result as an available feature for other applications. One enables "location services" and whatever subsequent applications or even webpages with one chooses to engage will have access to that particular service.
"Location services" may sound the same as "GPS", but it changes how I think of it from enabling a hardware feature of my device to enabling a suite of services which happen to use that feature. It's a change in how we think.
|Current AV system topology, with a|
switcher in the middle.
How is the world of AV different? In the world of AV too many of us still think concretely and too much of that concrete thinking is anchored on the bedrock of yesteryear, when the central element of most large systems would be a matrix switcher. Not too long ago, this was a reasonable idea. One would want to send the DVD player to the screen. Send a laptop to the videoconference codec, then send the output from THAT to a screen. Etc. Operation of the system becomes, at its core, an exercise in routing sources to destinations. Thinking about the system as a matrix router informs choices from initial system design all the way through implementation, especially when it comes to designing a GUI. In fact, GUI is, in some was, at the heart of the problem and the problem lies mainly in the touchpanel.