Build your vision and be better than your competitors.
Then less than 1 year later Google cancelled that project and now there is nobody to provide that service.
This made me imagine some poor, bright but new-hire Google PR employee realizing this popular (and quite correct) view of Google ("CANCEL ALL THE THINGS" [1][2]) frantically trying to figure out how to actually communicate to upper management (without getting fired) the blunt truth:
This ongoing strategy of announcing projects and promptly canceling them after a few years is incredibly damaging to the company. Google's "ADHD-like low attention span" to projects is anything but confidence-inspiring. :(
1. http://memegenerator.net/X-All-The-Things
2. HN likes numbered references and I do too
My take is that Google is less developer-friendly than Microsoft and Apple. Google does not rely on external developers as much, because so much revenue comes from web based, directly consumer facing products. Google is always trying new things, because they are looking for the next big user facing product. This might annoy developers who build against Google's APIs, but that is worth it because Google relies on users, not loyal developers. It is a fundamentally different approach from Windows or iOS.
A few examples
>AngularJS
>AOSP
>Google Maps
>GCN
>Chrome Dev Tools
>Polymer and Material Design
>Go
>Dart
I can tell my odd experience about Microsoft: my company reverse engineered many of its products and offered APIs around products without APIs. One day someone from QA sent us an e-mail offering help if some of these products have issues with Windows 7!
At the end of the day, all large companies have to dip their toes in new technologies, or die. Some of these projects will work out and others won't. Small companies do the exact same thing, except instead of announcing they are discontinuing a project they go bust.
My approach is not to get too tied to any vendor's technology, because if you do, you're setting yourself up for a fall. The rise of open source and standards has made this much easier than it once was, luckily.
In a sense it is a return to the MS that was before the IBM PC, when they were supplying office and development tools to all comers (MS Office got its start on Apple computers after all).
The presentation is here: https://www.youtube.com/watch?v=mpbWQbkl8_g&t=47m23s (starts around 47:23).
Understatement of the century. However, I see it as great news for you. If you're far along enough, and this proves to be something people want, you're a shoo-in for a buyout. Good luck and keep up updated.
In a recent episode of Silicon Valley, the billionaire president of a company said to his employees "I don't want to live in a world where someone else makes the world a better place, better than we do."
Your tone is pretty offensive. It would shock almost no one on this site that someone would like to build their own business without an aim to sell it or that someone would have philanthropic life-goals in general.
Many business owners who are bought out turn to philanthropic pursuits now that they've become fiscally stable.
Instead of considering any of the other options, or that the small company could actually compete with the larger company (hint: Google doesn’t operate most of their services outside of the US at all), the only real suggestion is "you’re in for a buy-out".
But then I thought about it. What a wonderful validation of our idea. And we think we can do it better.
Look at the angles and if you have to reshape your idea then do so. Maybe some competitive advantage you have will stick out or you'll develop it after seeing their offering. But think of this as a good thing. Investors love competition. It means there's a market.
Keep on going, the world needs more of people like you.
Could someone share a link to the original presentation? I'd love more technical details.
Is this SDHC or SDXC compatible? If they support SDXC, how do they reconcile "fully open source" with the fact that SDXC requires exFAT which is proprietary and protected by patents?
Building something like this requires an SD Slave Controller. It would be absolutely fantastic if they open source that! Fully verified and SDXC compatible? This makes me drool. Unfortunately the necessary information to implement and verify is walled behind NDAs (SD Association), unless of course you have reversed it with a logic analyzer. I don't think that's what Google has done, which makes me very curious.
If the slave controller is not open source, that begs the question of how data is transferred to the RTOS. A closed source core with DMA to whatever you run on it will exclude it from certain privacy-sensitive use cases.
If anyone at Google is reading this, consider using cores from cryptech.is for your crypto. You're already a funder so you might as well reuse them.
If anyone is interested in what I just said and you think you can contribute I would love to talk with you. Email me at [email protected].