How Google Is Challenging AWS • Hacker News Board

Re: How Google Is Challenging AWS

#171

Post by addicted » Fri, Dec 02, 2016, 7:05 AM UTC

foxylad wrote: post #112

user5994461 wrote: post #53

Earlier quoted context omitted.

> App Engine wasn't evidence of Google being a product company, nor does it exemplify the company's strategy. It was a grassroots project that for years didn't receive much leadership support, but was still allowed to launch and grow. App Engine was a precursor that came 5 years too early. The hype about serverless is only starting now.

We jumped on Appengine very early, and have never regretted it. It's remarkably stable, and not having to worry about the security issue du jour, scaling, or any other sysadmin stuff means we can concentrate on what we do best - building apps. I've been surprised how few people understand the value proposition, and how little competition there is. When I first heard about Azure I expected it to be PaaS, but it turned…

I'm pretty sure Azure began as Paas as well, and added Iaas later.

Re: How Google Is Challenging AWS

#172

Post by petra » Sat, Dec 03, 2016, 11:28 AM UTC

olimashi wrote: post #165

halflings wrote: post #151

Earlier quoted context omitted.

They definitely are for most customers: it is extremely expensive to gather and label enough data for a deep learning model to work correctly. It's very unlikely that you'll manage to configure and train your models + generate input data that Google lacks to make your model work much better than what Google already provide with their "generalist" API.

Say you are an insurance company and you want to use build a model that uses damage photos and meta data about car as a backstop to make sure that your repair shops aren't ripping you off. In this case you already have a bunch of historical labeled data and a pre-trained model is useless to you application. It doesn't help you that the pre-trained model can recognized 10 different types of cats, you need a model trai…

What about combining your own model with what Google offers you, especially when you might not have enough data or expertise?

Re: How Google Is Challenging AWS

#173

Post by lambardy » Sun, Dec 04, 2016, 11:57 PM UTC

foxylad wrote: post #168

detaro wrote: post #113

Earlier quoted context omitted.

Isn't Azure Cloud Services pretty close to Appengine?

Not as I understand it . Both AWS and Azure force you to use machines - you may put them behind load balancers, and they may start up automatically when required, but you still need to design the system and do provisioning and plumbing to make your application working. With Appengine, you don't know anything about the hardware of software your application is running on - you simply upload your app. I haven't used Azu…

Azure has a ton of serverless components. Functions is their lambda equivelant. Azure has many services you can create apps and capabilities without standing up a sever. Like anything else it has some pros and cons.

Re: How Google Is Challenging AWS

#174

Post by cobookman » Mon, Dec 05, 2016, 8:03 PM UTC

ap22213 wrote: post #59

cobookman wrote: post #12

Earlier quoted context omitted.

Email me at bookman@google.com and I'll be sure to start internal conversations around what we can do to help you out.

Cool - I'll try to get someone on my team to give you an email.

Hey ap22213. Never got your email. Just following up to see if you've resolved your issues with GCP, if not feel free to contact me at bookman@google.com

Have a great day.

Re: How Google Is Challenging AWS

#175

Post by inflagranti » Sun, Dec 11, 2016, 3:32 AM UTC

inflagranti wrote: post #136

cle wrote: post #133

Earlier quoted context omitted.

Silk is a fork of Chromium, Amazon just piggy-backed on Google's hard work. Just like Fire OS itself (a fork of Android).

You mean the way Google piggy-packed on Apples work which in turn piggy-backed on KDEs work? Amazon did an extension to optimise rendering on small devices, which is complexity wise not too far off to what Apple & Google contributed to the rendering engines, which at the end is the tricky bit an a browser, not the Chrome.

Really don't understand the downvotes. Whether they gave back to the community or not is another story, but they did piggy-back on previous code, even though adding a lot themselves and giving back a lot, but it still built on massive existing work.