233 karma · joined July 22, 2013
(Source: have worked at GDS for the past couple of years.)
That being said, it almost never makes sense to drive a car inside central London anyway as the public transport is very reliable and has almost full coverage, and it's dealing with a very different problem in the first place (old horse and cart windy roads adjusting for the modern age).
I used to work on a virtualised Windows machine (work mandated) and the only usable accessibility option was a high DPI setting. The old Lync client worked perfectly with this, obviously dating back to an age where they cared about accessibility. Skype for business completely ignored system DPI settings, made certain things huge with other things being tiny.
The spacing was the biggest issue - literally 30-40% of my 43" monitor would often be taken up by spacing around icons etc on the app.
It really felt as though they just stopped putting as much effort into UX, accessibility, usability. Lync felt like a professional IM client, Skype for Business felt like a half baked bodge.
I have yet to see a compelling/coherent argument for why they shouldn't.
As a partially sighted user myself, I find it infuriating when web developers try to override browser behaviour/modifications (e.g. blocking pinch to zoom). If we go down a path where users can't modify pages, we are taking a huge step backwards.
AMP, also made by Google, seems to somehow get around this browser setting, making AMP sites unreadable and therefore completely useless to me.
Why does Google have these obvious discrepancies between their own products?
Seems very odd for a seemingly minor iterative update to pop up out of nowhere after such a long time otherwise.
* The update, not Google Glass itself
One of the most endearing things was when somebody would try to test out their very limited knowledge of English on me at random, they'd often seem quite proud of themselves and I was always happy to oblige.
(Incidentally my girlfriends home province is also Xinjiang!)
What do you plan to do with the "recommendations" feature?
A good example of where, even the highest level of automation in an aircraft, failed to assist in an emergency was Qantas Flight 32 [1]. A physical failure on the plane caused sensor and control failures, something rendering AI almost completely useless. Admittedly, humans can also have failures and this has lead to many crashes before, however humans have also used exemplary skill, experience, and abstract problem solving to correct mechanical failures in aeroplanes countless other times.
Anybody who has actually, or is currently, studying AI will know that there are fundamental differences in programming "AI" and some self aware magic computation which is almost entirely unfathomable. With current knowledge, at least, the only way to have any sort of learning is to design and implement algorithms to do so. There can of course be incredibly abstract knowledge base designs and the computation can assimilate incredibly complex knowledge from those, however it is almost a logical fallacy to suggest that we would ever lose control of something autonomous due to some sort of "rogue agent".
Of course, there are very real risks with something like AI, but it's much less sinister than what the article suggests. For example, faulty code or errors in the knowledge base could lead it to make a bad decision, but humans can also do that.
I don't think we should be dismissing the risks necessarily, but I do believe that it is completely far fetched to say we would be making the worst mistake in history if we are to dismiss a film as science fiction!
They're a cool company and all but I agree, fortunately things like this have a way of sliding off the HN frontpage fairly quickly.