This week has seen the technology world converge for the annual Consumer Electronics Show (CES).
No sooner have the Christmas and New Year celebrations concluded, then its time to head stateside to see what weird and wonderful innovations are on display.
CES has traditionally been a launchpad for all manner of electronics – smartphones, tablets, washing machines, fridges and robots – and this year was no different.
But the technology at CES has ramifications for the enterprise technology world too, so its important to keep an eye on what’s happening.
So how up to date have you been keeping over the past week? Do you know what has been making headlines and what new products will be hitting the shelves in 2018 and beyond?
Why not find out with our quiz and let us know how you did in the comments? Good luck!
More bad news for Google. Second time in less than a year that some part…
Federal office that tackled misinformation and disinformation from hostile nations is closed down, after criticism…
After Nvidia admits it will take $5.5 billion charge as Trump export limits of slower…
Trump continues to target his former CISA head, signing a new executive order targetting Chris…
Two Chinese retailers warn customers in America that prices will increase next week, as Trump's…
Engineer Cristina Balan wins latest round in her long-running defamation claim against Elon Musk's EV…
View Comments
The question here is not that Apple did anything wrong in making iPhones with failing batteries last longer on a charge, and avoid unexpected shutdowns due to the failing battery's low current. The question is why Apple didn't inform people that it was making a change to improve the user experience, by avoiding unexpected shutdowns on iPhones with failing batteries by slowing the processor to accommodate the inadequate current provided by the failing battery.
That question should be followed up by asking how many times has any operating system updates, from ANY developer (including Apple, Google, Microsoft, Amazon, etc.) included a special notice to the user of EVERY code change made to improve the user experience.
The answer is that this is NOT a common action, and that users would be inundated with a deluge of information if any developer made a point of notifying the user of ALL code changes with each update, and the effect each would have to improve their user experience.
Unless someone prefers to have their iPhone with a failing battery shut down unexpectedly, and NOT be useable for a longer time (which no sensible person really wants), then this whole issue (and some people's "indignation") is totally senseless.