Proprietary drivers, firmware blobs and ASICs are a national security threat. Without open code reviews, auditing and functional verification it's impossible to trust there are both a minimum of exploitable bugs and/or backdoors in a given software-hardware stack. This may require some sort of confidentiality rubric but there's no shortcut to getting around this vital need.
Workaholism without aligned interests (ie, real, founder-class stock for employees, eg a co-op) isn't rational except for people whom sell their whole existence to a company, but that's also a recipe for burnout.
As the basecamp folks said, "Fire the workaholics."
Google lacks fundamental business and product management skills.
Creating an "open platform" encourages device makers to polish it only for their needs but not upstream features and fixes to competitors (OS fragmentation) and let multiple, insecure versions run forever that rarely get updated (legacy fragmentation). Plus, Linux security is usually an oxymoron which Fuchsia may address. If Google wants their platform to survive, they're going to have to require approval for apps and devices, and stipulate things like UX usability and mandatory OS patches.
PS: There are thousands of servers run by handset manufacturers and telcos that are required for some features of mobile devices to work at all. For example, Motorola Mobility smartphones' depended on their own servers for many social media features to work. These backend-heavy designs are supremely easy to brick, disconnect and invade privacy of users, en masse, for profit and for government spying.
- Worker bees will stay because they're clueless and don't have the initiative to keep moving.
- Pressure from on high to fudge performance reviews downwards to "save the company money." (At where my mom worked, a middle manager blanket reduced all subordinate reviews down because BS: "people are overly generous.")
If you want least turnover / most morale / most productivity, pick people whom can grow the most and grow them until they no longer can keep up or find something else. Develop people (training, mentoring, promotions, bonuses, raises, perks, etc.), don't just consume them as static widgets to fill a hole.
Everything but the actual private key/parameters should be open-source, vetted and approved before going forward on a cryptocurrency... no magic obscurity when it comes to money. Otherwise, scams and/or vulns lead to amateur-hour fail.
Add some nixie tubes, and you have a steampunk wet dream.
Find ye parts:
http://octopart.com http://findchips.com