161–170 of 221 posts
"The unit could report compound annual growth of 55% between 2018 and 2022, and reach annual sales of about $38 billion by 2025, the analysts wrote." I'm curious how they're making basing these predictions since Google Cloud revenues aren't currently reported.
Earlier quoted context omitted.
It is today, but it won't last. As automation tooling gets better the barriers to entry drop and competition kicks in and lowers prices. You can see it already: Aws are constantly lowering their prices. It's not just to be nice, they're competing hard.
You forgot storage and the huge lock-in that storage has. It would cost $850,000 to move 10PB of data out of a cloud. People aren't going to do it. They aren't going to be able to afford to do it.
Earlier quoted context omitted.
You fail to provide any evidence or even personal anectode to support any of your assertions. You make claims, other fellow users counter your argument with objective statements, but you ignore everything and opt to double down on more baseless assertions. That is not helpful at all.
I mean. I don't know what you want me to say. I'm not trying to prove that AWS UX is better than GCP or vice-versa. Perhaps GCP has features like the ones mentioned above that improve the whole developer experience, but that's not what I'm arguing here. I'm just trying to elevate the argument to another level and explain why all of them have horrible UX and it's not even worth it to compare them since the bar is so l…
Earlier quoted context omitted.
Anecdotal story: I was working on a personal project where I wanted to try a "server-less" setup and I found Google's firebase authentication pretty handy and when I was looking into Firestore I found these handy videos on Youtube that Google made that I thought were pretty good introductions ... and they even updated the videos here and there so they weren't up to date. I felt like I understood how things worked pre…
Have you tried aws cli though? The whole thing is 100x easire in the command line and the documentation is 1000x better. There's even help pages you can get as you type in help. aws s3 help basically list a bunch of option to deal with s3 and you could read through and do exactly what you want. Not saying that console are useless but AFAIK all possible action through console can be a command that's (probably easier).
I am interested to know the valuation of AWS. If the values are apart then it makes sense that AWS was ahead of teh game. If GCP has caught up then that would be blazing-fast improvement.
From Bloomberg re GCP: "The unit could report compound annual growth of 55% between 2018 and 2022, and reach annual sales of about $38 billion by 2025" AWS q2 2019 was was 8.4 billion so AWS in 2019 is near where GCP is projected to be in 2025. AWS q1 to q2 growth was 37%, so much slower growth than Azure and GCP. From Barrons earlier this year: "He sees AWS revenues of $36.1 billion this year, growing about 31% a ye…
Earlier quoted context omitted.
Another thing that contributes to the mess of AWS UI is their docs. Probably a personal preference thing, but I don't like their cluttered UI for their docs either. Maybe if they had some developer advocates or pay websites/blogs to post about how to use all 300+ services of AWS (probably an exaggeration... but looking at their dropdown probably not) then it would be better for developers or even companies to come on…
Actually I really like the AWS documentation, even more since they launched their public knowledge center [1], which offers answers for common use cases. And AWS does have of course evangelists blogging about a lot of stuff. You should check out their blogs overview page [2] which lists 29 new posts since the beginning of October alone! [1]: https://aws.amazon.com/premiumsupport/knowledge-center/ [2]: https://aws.ama…
Not surprised. If AWS can't make their UI a bit more user-friendly (especially for beginners) and remove their AWS Educate for students (which by the way is horrible), I think a good chunk of developers and possible institutions might move over to GCP. Other that UI, I think GCP in some instances may be cheaper (pretty sure I saw some instances that were cheaper... although I can't say for sure).
Is it really just the UI that's better designed in GCP compared to AWS? I find the "better designed" thing seems to apply to most aspects.
Earlier quoted context omitted.
I'd say it was wrong. Amazon and Microsoft now make huge amounts of money from their clouds. It can't be that low margin! But I feel like their real mistake was trying to do things right, rather than compatibly. I think Google Cloud Engine is undeniably a better system than ad-hoc Linux VMs. But nobody really wants to rewrite all their code to work with it.
Google Compute Engine offers ad-hoc VMs. Google (and Amazon) have many offerings.
Google is the only provider with a good portal to their partner program. They can actually communicate and we now have a dedicated account rep.
Earlier quoted context omitted.
I never have any luck figuring out how to do most things in GCP. The disjointed UIs, the documentation that is out of date, etc leave me just going back to AWS.
I had such a different experience when I was trying out the two platforms in parallel about fours years ago. I came from a background where we'd created/ran all of these kinds of services in-house - simply because we started building our stuff before AWS/GCP existed in any meaningful way. Anyway, after switching employers four years ago I had a greenfield project. I had zero investment in either platform. (I had join…
* GCP gave me the feeling it was designed with taste, through every layer. Comparing this to the desktop platform fight; think Apple. Quality over volume.
* AWS gave me the feeling it was designed without taste. Think Microsoft. Volume over quality.
I'm talking about the combination of service design criteria, APIs, documentation, etc.
Another way of thinking about it: GCP is clearly designed by hackers schooled in the ways of UNIX over a very long time. Simplicity and elegance is valued very highly in terms of designs. For AWS: Simplicity is clearly not a design goal.