News for hackers. Stuff that matters.
Re:SFO near miss might have triggered aviation disaster by acchow on Tuesday July 11, 2017 @02:18AM (#14741969)
> It is a very Silicon Valley thing to assume that everyone else is an idiot and needs to be disrupted, with not a thought given as to why things are the way they are.

This kind of thinking has also lead to a ton of success in Silicon Valley. See Tesla for example.

Re:SFO near miss might have triggered aviation disaster by vintageseltzer on Tuesday July 11, 2017 @02:39AM (#14742051)
This kind of thinking led to Juicero.
Re:SFO near miss might have triggered aviation disaster by pdelbarba on Tuesday July 11, 2017 @11:43AM (#14745107)
And applied to aviation you get the Piasecki PA97
Re:SFO near miss might have triggered aviation disaster by dx034 on Tuesday July 11, 2017 @02:39AM (#14742049)
Did Tesla really disrupt the car market? Sure, everyone is now building EVs but that already started before Tesla became successful. They have no market power on the overall car market.

Companies like Uber, Google, Amazon certainly disrupted markets but I wouldn't be so sure about Tesla.

Re:SFO near miss might have triggered aviation disaster by mikeash on Tuesday July 11, 2017 @12:13PM (#14745356)
Nobody was building long range EVs before Tesla. Short range city cars like the LEAF are really a different category.

Volvo has credited Tesla for pushing car makers into EVs, so at least one incumbent thinks that: https://electrek.co/2017/05/17/volvo-tesla-says-stop-diesel-...

Audi seems to as well, although it's not quite as clear: http://insideevs.com/audis-electromobility-boss-i-hate-to-ad...

Re:SFO near miss might have triggered aviation disaster by coldtea on Tuesday July 11, 2017 @02:36AM (#14742035)
>This kind of thinking has also lead to a ton of success in Silicon Valley. See Tesla for example.

Well, not exactly a role model for success. 2016 was the first time they made any profit in all those years -- and its uncertain if 2017 will follow.

And it might still be beaten up in all its markets (electric cars and eventually self-driving ones), not a sure winner yet.

Re:SFO near miss might have triggered aviation disaster by justinjlynn on Tuesday July 11, 2017 @02:38AM (#14742047)
A broken clock is correct at least once a day.
Re:SFO near miss might have triggered aviation disaster by idlewords on Tuesday July 11, 2017 @02:51AM (#14742095)
That used to be true (twice a day, even), but now it just flashes 12:00, or the screen is dead.
Re:SFO near miss might have triggered aviation disaster by caf on Tuesday July 11, 2017 @03:48AM (#14742304)
A clock that flashes 12:00 is still right twice a day.
Re:SFO near miss might have triggered aviation disaster by glenneroo on Tuesday July 11, 2017 @04:44AM (#14742546)
Unless you live in a country which uses 24-hour clocks, which is most of the world.

Source: https://en.wikipedia.org/wiki/Date_and_time_representation_b...

Re:SFO near miss might have triggered aviation disaster by caf on Tuesday July 11, 2017 @07:38PM (#14748999)
Do unset clocks flash 12:00 in locations that use 24-hour clocks, or do they flash 00:00?
Re:SFO near miss might have triggered aviation disaster by glenneroo on Wednesday July 12, 2017 @12:08PM (#14753704)
I can't honestly say I ever paid attention, but I just checked all clocks I could find, one flashes 00:00 and the other 0:00. Most if not all clocks I've used had a 12 or 24-hour mode, not sure what happens if you set to 12-hour and unplug it (probably just reset to defaults).
Re:SFO near miss might have triggered aviation disaster by idlewords on Tuesday July 11, 2017 @10:46AM (#14744594)
Flashing is an error condition.
Re:SFO near miss might have triggered aviation disaster by justinjlynn on Tuesday July 11, 2017 @08:30PM (#14749239)
Indeed, a broken modern digital clock is likely to just be blank.
Re:SFO near miss might have triggered aviation disaster by Kliment on Tuesday July 11, 2017 @03:50AM (#14742313)
So it's correct at 12 and possibly at midnight too