Just like Smart Cell Phones are planned obsolesence, it woul dseem like the IoT is heading in the same direction UNLESS backward capability in browsers are ALWAYS maintained.
The cell phone seems to be the "universal remote" of choice, but the browser is least updated, The html is stored on the Inter net of THING and the external browser executes it.
So, aren't we creating a dying bread before it even gets off the ground?
You buy an IOT.
It uses a particular browser. (cell or otherwise)
Browser depreciates a certain aspect of the IOT's html.
IOT becomes useless.
IOT has a short lifespan and ends up as ewaste.
The short cycle repeats.
Aside:
At one point I was developing in a early version of LabVEW when it was in the process of changing to cross-platform. It was not quite mature, so any fix I made, might have been also fixed in a new version. Functions I had to create were then available in a new version.
One function, I fondly remember was "flicker fixing". Numbers in indicators would flicker unless you played games. Error handling did not exist. With LabView, you always have to upgrade, Backwards compatibility doesn't exist. Once a VI is converted to a higher version, you can't go back. VI's as instrument drivers are generally only available in the current version of LabVIEW. So, National Instruments has a perpetual money making machine.
I doubt IOT makers will keep continuing "developing" their products so it maintains the functionality on all browsers. I do remember where this site only work with IE etc. I also know that their are development libraries that try to work out the idiosyncracies between browsers and browser versions.
I have a very old phone that runs Opera mini. The original browser died long ago. AllAboutCircuits (AAC) is usable. I can't find a way to log on and the data of each post is missing.
This also applies to a Samsung Smart TV too. Flash is not supported and networks use flash based players.
IoT has a bad smell to it.
The cell phone seems to be the "universal remote" of choice, but the browser is least updated, The html is stored on the Inter net of THING and the external browser executes it.
So, aren't we creating a dying bread before it even gets off the ground?
You buy an IOT.
It uses a particular browser. (cell or otherwise)
Browser depreciates a certain aspect of the IOT's html.
IOT becomes useless.
IOT has a short lifespan and ends up as ewaste.
The short cycle repeats.
Aside:
At one point I was developing in a early version of LabVEW when it was in the process of changing to cross-platform. It was not quite mature, so any fix I made, might have been also fixed in a new version. Functions I had to create were then available in a new version.
One function, I fondly remember was "flicker fixing". Numbers in indicators would flicker unless you played games. Error handling did not exist. With LabView, you always have to upgrade, Backwards compatibility doesn't exist. Once a VI is converted to a higher version, you can't go back. VI's as instrument drivers are generally only available in the current version of LabVIEW. So, National Instruments has a perpetual money making machine.
I doubt IOT makers will keep continuing "developing" their products so it maintains the functionality on all browsers. I do remember where this site only work with IE etc. I also know that their are development libraries that try to work out the idiosyncracies between browsers and browser versions.
I have a very old phone that runs Opera mini. The original browser died long ago. AllAboutCircuits (AAC) is usable. I can't find a way to log on and the data of each post is missing.
This also applies to a Samsung Smart TV too. Flash is not supported and networks use flash based players.
IoT has a bad smell to it.