I'm considering doing a side-project to auto transcribe minutes from voice recognition for the meeting and index all that data so its searchable and also plugable to existing enterprise systems through REST API. Does that sound something useful?
Smart image CDN. Process images on-the-fly, store and serve with CDN of your choice. No need to setup any imaging infrastructure (storage, processing and CDN delivery) for web/mobile apps.
Developers get started within 5 mins to signup, point us to where your original images are and replace the <img src=""> from your domain to the new origin you just created.
One of the features is to serve the right image format which can reduce image bandwidth on a page anywhere between 40% to 400%, or more.
That's a different issue. I think what @lintiness is trying to say is that just because a market went up in the past does not mean it will in the future. Survivorship bias is absolutely huge here.
Most people forget this, but if you look at global markets since the early 1900's, there were several that went down and never came back up. Germany's markets failed on at least one occasion and never came back. A good paper that addresses part of this is here: http://www.researchgate.net/publication/4913017_Global_Stock...
Depression and war do many things that create discontinuities. Most people don't come close to thinking about those because they aren't knowledgeable enough to even understand how strong the survivorship bias in their current local market like the US.
The SoC (card sized) has everything you'd need, not just the connectors to the several I/O and networking interfaces you may need. You will hook in connectors are you like with the 400-pin interface on the SoC and get going.
There's one serious problem with using 3rd party Imaging SDKs or utilities to build your service on: You're stuck with their flaws and you can't do much about it.
We have written our own image processing SDK, using only encoders which are 3rd party (libpng, libjpeg, libwebp etc), rest is all handwritten, GPU optimized code. The rationale behind it was to be able to tweak/optimize any feature.
Currently, only AWS offers GPU instances. There are other, smaller providers like Nimbix or Peer1 but they offer bare-metal instances. With AWS, they currently have Grid K520 GPUs which is targeted for public and private Clouds.
The gist of this paper is that non ECC memory does not zero the memory but it conveniently skips the fact that public or private Cloud uses either NVIDIA Tesla or Quadro series cards, both of which have ECC (one of the main reasons they're expensive than say GTX Titan which offers same single/double-precision performance but does not offer ECC). No one really uses GeForce series cards for anything serious and definitely not virtualization so even though this is a vulnerability, it may not effect more than 1e-10% of virtualized GPUs out there
